Better debug mouse #20
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "kistaro/chameleonic:better_debug_mouse"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Debug mouse is now its own module, so it can be separated from the hint system, since it is useful for more than just positioning hints. It now has the following enhancements:
Sprite 50 is now the mouse cursor. Color 15 is color cycling for debug readouts.
Debug mouse features can be disabled by commenting out
add(real_modules, debugmouse)
.I've done a little bit of golfing but this is stiill a token expense. I'm going to write a crappy sprintf function to save tokens everywhere we're assembling strings from their component parts.
This has a merge conflict with writing hints for the first few stages, put in whichever you prefer to put in first and let me know and I'll resolve the conflict.
aefdfeb99c
toe878717c31
I fixed the merge conflict.
I'm not opposed to this, but I think we're likely to be using text hints much less from here. I'm also not sure we need map cell coordinates -- can we comment those out for now to save space?
I strongly agree with making this a module.
I've removed the map cell coordinate display. I thought there was a point where I would have found it really useful because I was counting map cells for something and kept getting it wrong, but now I don't actually remember what that was. Maybe I was trying to line up level exits or something? In any case, I can just divide by 8 myself.
I've also removed the parentheses because those aren't necessary.
I expect to include text in hints regularly -- I think single words without specific locations, but in vaguely relevant locations, will be a useful and interesting variety of hint. But, I think the shape-cycling cursor is annoying, because it is usually not the shape I want it to be; I've changed from cycling between options to choosing a shape based on which mouse buttons (either or both) are pressed. I can also save 3 tokens by removing the
not c or
part of the "do we draw the arrow or a character?" logic, which means the middle mouse button (alone) would make it display[NIL]
instead of any of the cursors.