Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Posn not correctly interpreted for Combo and Button objects #353

Open
mkromberg opened this issue Jan 17, 2025 · 0 comments
Open

Posn not correctly interpreted for Combo and Button objects #353

mkromberg opened this issue Jan 17, 2025 · 0 comments
Milestone

Comments

@mkromberg
Copy link
Collaborator

Run DemoTreeView. Notice that the TableSize, Function, CalcBtn, PasswordField controls are all created with the first element of Posn =210.

{"WC":{"ID":"F1.TableSize",...,"Posn":[210,10],"Size":[23,100],"Text":"10","Type":"Edit"}}}
{"WC":{"ID":"F1.Function",...,"Posn":[210,120],"SelItems":[1,0,0,0],"Size":[23,100],"Text":"+","Type":"Combo"}}}
{"WC":{"ID":"F1.CalcBtn",...,"Posn":[210,230],"Size":[23,100],"Type":"Button"}}}
{"WC":{"ID":"F1.PasswordField","Properties":{"Event":[["Change",""]],"Password":"*","Posn":[210,340],"Size":[23,100],"Text":"Password","Type":"Edit"}}}

These used to be drawn on a line, but now:

Image

@mkromberg mkromberg added this to the Blocking milestone Jan 17, 2025
@mkromberg mkromberg changed the title Posn not correctly interpreter for Combo and Button objects Posn not correctly interpreted for Combo and Button objects Jan 17, 2025
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

No branches or pull requests

1 participant