Skip to content

Conversation

@BrokenRafterFarms
Copy link

Added some handling so that macros are forced to IDs of 0-255 which is the standard for any VT version less than 5. Also updated so that all other object types now start an ID of 256 and count up.

If you try to add a macro after you have filled all the IDs from 0-255 you get this popup:
Screenshot 2025-07-23 at 8 46 08 AM

If you try and edit a macro higher than 255 it shows this:
Screenshot 2025-07-23 at 8 47 46 AM

I wanted to have it say "Macro IDs must be 0-255!" but I couldn't figure out how to make it stay... See the code in: src/object_configuring.rs

I have attached the pool that I used to test the edge cases (trying to add more macros that 255 and editing a macro to and ID greater than 255).
object_pool_macro.iop.zip

GwnDaan and others added 8 commits February 11, 2025 19:52
also introduced filter/search bar, and sorting of objects
Improved Macro Support. Since Macros until VT Version 5 can only be IDs 0-255.
Added validation to restrict Macro object IDs to the 0-255 range in both object creation and configuration. Introduced a modal error window in the UI for invalid Macro IDs and improved conflict messaging in the object configuration panel. This was not fully achieved...
Changed the rustflags for the wasm32-unknown-unknown target to use '--cfg=wasm_js' for improved compatibility and clarity.
Fixing some merge errors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants