Coding a Graphical Bar, with Base ASM (v6.3.4)

As a warning to anyone utilizing the memory calculator to view the graphical bar memory layout, the disabled grey-out button(s) will suppress "mouseup" events when utilizing the mouse-drag feature (you click and hold the "Click & drag to adjust", if you release the left mouse button over a disabled element, the page thinks you are still holding until you click and let go again). Should be a minor issue though.

Accepted; reviewed the incoming JavaScript-only changes in the git commit history for this tutorial and tested with Firefox (for functionality, not quality of the code). Works.

Moderated with:
- Windows 11 Home
- Google Chrome

Very thorough update and lots to go through. Took a while to get to everything but it all looked solid from what I read.

MinecraftGamerLR Make sure you have the GraphicalBarDefines folder in the right place. In the main directory of uberasm tool, for example.

Every time I try to install the example pack, I always get the "Macro Library File Not Defined" error. What am I doing wrong??

Tymare Thanks. I went all out, adding tons of features to it than just a basic rectangular meter to give it a more appealing look.

i like it. it look good

Moderated with:
- Windows 10 Home
- Google Chrome

Incredibly thorough documentation on graphical bars with tons of examples. There's a lot here so I might've missed something but it's overall quite solid. Hopefully people find this useful.

Black Goku Yes, just edit the defines that would point to JSL !SharedSubroutineDefines to instead a label that would point to its code (a subroutine within the sprite code ASM) or Pixi's routines folder (must be %SubroutineFilenameFromRoutinesFolder()). And then move (cut/copy, then paste) the code to its code or in the routines folder.

I prefer the shared subroutines patch because it makes it accessible on any ASM resource (like have a bar for the HUD and as a sprite) than just uberasm tool or pixi. Another reason is that you cannot call a subroutine within another, separate subroutine file in a daisy chain -like fashion:

Is there some way to use the boss health mether without the Shared Subroutines Patch?

OAM (sprite tile) support added.

coool

Since I've already tested the codes provided in an earlier version, all that there is to do is analyze the new routine and read the small changes made. No problems found, so I can accept this update (as I keep reading waiting docs for some time before even claiming them).

Routines tested with: UberASMTool 1.3 and 1.4, SA-1 1.31, LM 3.03 and ZMZ 1.08.

Missing info successfully added. So, I do not have reasons to reject.

I apologize if I was too harsh on you in the last removal; but you cannot deny that you improved as a result: the document is readable, easy to follow, and by it I can easily made the examples work, as an average user. Sure there'll be eventual ASM bugs here and there (as a perfect ASM code of this caliber is difficult to obtain); however, since the focus of this section is the document per-se, and the basic idea worked well, as the examples themselves... I don't see another consideration other than an approval. Thus, I'll accept this document. Kudos to you, GHB; as I said, you improved a lot.

and changing JSR to JSL too.

This tutorial is excellent for those coding their special bars to use on their own hack. A small note, if you are using UberASM tool, don't forget to convert the RTS to RTL or you'll get crashes.

@Tsutarja

The two extra tiles are end tiles. Make sure you read the readme. I tested this using gamemode main 14.

this doesn't seem to work with Advanced Super Statusbar.

i just see the first tile, and it was supposed to appear 9 (since !MiddleLenght is 7)

tested on statusbar_code.asm

You can even make a geometry dash progress bar.

Document was verified by Sonikku.

Fixed an issue:
One of the images describing the pieces of an 8x8 says 3/6 twice.

-Fix the Sa-1 issue if you set middle length to other than a power of 2.
-Fix the bar drawing looping routine that I've forgot to include the end tiles for old HUD.
-Fix another problem with the rounding on non-sa-1 when you use MaxQuantity a large value (like 400).

Yeah, this code requires a HUGE explanation that it doesn't qualify to be on the uberasm thread. It's the kind of post that should be submitted to a section instead of a thread. I call them [BASE ASM], because it's an asm code for many uses, but too big of an explanation that needs to be a section submission instead of an ASM library, plus, the submission section is a big out-of-the-open area than a download linked from the forums.

Hopefully, in the future, doesn't get rejected because this is mainly code for many uses or someone changed their mind on accepting this. The smw disassembly is a code and a document, for hacking smw.

Honestly, probably this would fit better on the UberASM thread (or maybe in a UberASM section), but since you included a full document explaining how your system... I don't know. Since the Staff Team didn't have any opinion regarding this and everything seems ok, I'm approving this.