Feature/form editor explicit gadget #347
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…citId - Add explicitId to FormGadgets/FormWindow structure (declare.pb) - Parse "#NAME=NNN" gadget/window IDs on load and map FormGadget/FormWindow enumeration values (opensave.pb) - Generate fixed enum assignments while keeping gadget/window calls as "#NAME" (codeviewer.pb) - Preserve and edit "NAME=NNN" in property grid; split/commit into variable + explicitId (mainevents.pb)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds support for explicit gadget IDs & explicit window IDs in the PureBasic Form Designer property field, using the syntax:
ID13310=13310orGadget1=1008(variable=explicit numeric ID)The generated code will keep the variable name as-is, while the enumeration constant gets the explicit assignment:
Motivation
Some projects require stable, predefined numeric IDs (e.g. compatibility with existing code, external bindings etc.). Until now, the Form Designer only supported automatic IDs (#PB_Any) or non-explicit enumeration constants, making it hard to keep IDs deterministic across edits/saves.
Behavior / Rules
The property field
variablemay containName=Numberto define an explicit mapping.Code generation outputs
#Name=Numberin Enumeration FormGadget / FormWindow.Gadget/window creation uses
#NameorNamefor Procedure Open...Backward compatible / non-breaking: If a property value contains no
=, the Form Designer behaves exactly as before (same parsing, same code generation).