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

Weird behavior when editing sublcass name and header #730

Open
FredEPr opened this issue Mar 23, 2022 · 1 comment
Open

Weird behavior when editing sublcass name and header #730

FredEPr opened this issue Mar 23, 2022 · 1 comment

Comments

@FredEPr
Copy link

FredEPr commented Mar 23, 2022

I found a weird behavior when editing the subclass name and header of a control. To reproduce it add two buttons to a layout and do the following:

  1. select first button
  2. add anything in its wxWindow -> subclass name
  3. add anything in its wxWindow -> subclass header
  4. without removing the focus to the header text control select the second button
  5. select the first button

The subclass header of the first button will contain "forward_declare". If between steps 3 and 4 the text control loses the focus the problem will not appear.

It's also next to impossible to remove the subclass name and header values once they have been filled. Sometimes the old value will come back or sometimes "forward_declare" will appear.

I'm having those issues with wxFormBuilder 3.10.1.

@sodevel
Copy link
Member

sodevel commented Mar 24, 2022

This is a known problem, see #543. The value of the checkbox property is moved into the header value. This happens when a data transfer between the wxPropertyGrid and the internal data model happens. I am still not entirely sure why this happens, but i think this is because wxFB uses the display variant when it queries the value stored in the wxPropertyGrid and this variant drops empty values.

This is kind of a fundamental problem how wxFB uses wxPropertyGrid, it does a great amount of work to use it "wrong" by overriding wxPropertyGrid integrated functionality, but this fails when using composite properties like that subclass property.

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

2 participants