SBARINFO

[Kinsie]

Do I need to?

For some reason the example on this page crashes r620 for me.

[Project Shadowcat]

Sounds like the latest revision hasn't been uploaded yet as both 621 and 622 address issues with SBARINFO. I could have sworn the changelog was already up to 622, but I saw for myself that sourceforge is only up to 620. You may need to do a manual compile

[Kinsie]

Ah, that'd probably explain it.

[Blzut3]

I forgot to mention on there you need to define INDEXFONT and STATUSFONT. These are given on the [wiki]FONTDEFS[/wiki] page.

I have the 3rd update. With this, the Heretic status bar becomes possible (minus the enhancements in ZDoom), so I should be ready to shift to Hexen's status bar. Below is the changelog:

Code: Select all

- Added drawshader to draw Heretic style transparency gradients.
- Added artiflash flag to drawselectedinventory.
- Fixed: Drawgem used the wrong operator when determining the chain size.
- Fixed: ZDoom would crash if an undefined font was used.
- I also started cleaning up the source a little.  I have been informed that 
  when checking for flags the "== flagname" is redundant.

[Graf Zahl]

- I also started cleaning up the source a little. I have been informed that
when checking for flags the "== flagname" is redundant.[/code]

Please don't do this when assigning to bools. It produces warnings in VC++.

[Blzut3]

- I also started cleaning up the source a little. I have been informed that
when checking for flags the "== flagname" is redundant.[/code]

Please don't do this when assigning to bools. It produces warnings in VC++.

Really? I guess it is a good thing I'm removing them. Or are you saying that bool something = (cmd.flags & flagname) == flagname; is correct?

[Graf Zahl]

See my latest commit. I had to fix these assignments because they produced conversion warnings.

[Nash]

Nice work, Blzut and Graf.

Hey you know, this is turning out to be a pretty big monster, and you know, if it works really well... how about exporting all of the games' status bars into an SBARINFO lump in zdoom.pk3?

[Blzut3]

Although it does make fairly accurate status bars, they are not perfect. All games make the fonts monospaced (as they do not use ZDoom's fonts directly). SBarInfo on the other hand will space the font on the fly, so purist would not like it.

[Graf Zahl]

It also works differently. For example, the key display in Doom's status bar is not limited to Doom's keys. It automatically selects the first 6 defined keys. For the custom status bar this is different and since mods know what keys they have (normally) the different approach there is ok.

[Jimmy]

Blzut, would it be possible for you to make custom Strife objective screens possible in the near future? Might be a bit of a burden, and I love what you've got here already, but I think these objective screens will need to go in eventually to cover Strife's status bar, so what do you think?

[Blzut3]

Well Hexen comes first, but of course I plan on supporting everything I can in Strife. After that I want to get all the ZDoom enhancements down, and then I shall open it up to requests.

[AFADoomer]

There is a typo in the source... "noatribox" should be "noartibox".

Are you going to add support for positioning items relative to the top of the screen, regardless of if the status bar is scaled or not? Right now, I can make a bar that has keys, or inventory, or whatever, at the top of the screen, but if I use the scaled status bar (or hud), that is not stretched to fit, I now have items that are in the middle of the screen, floating in the middle of my field of view.

[Graf Zahl]

fixed the typo

[Blzut3]

Graf, would it be improper to have a force scaling option? This would solve the positioning at the top of the screen and for HUDs like seen in the Doom alpha.