Skip to content

valuer.go toValue: do not use a text representation for nil pointers#1444

Closed
rcoreilly wants to merge 4 commits intomainfrom
valuer
Closed

valuer.go toValue: do not use a text representation for nil pointers#1444
rcoreilly wants to merge 4 commits intomainfrom
valuer

Conversation

@rcoreilly
Copy link
Member

because List and Table widgets will make those for empty rows, but when they later are used, the widget remains a text widget which is unacceptable behavior. fixed a crash on TreeButton -- any other issues can be fixed in a similar manner.

… because List and Table widgets will make those for empty rows, but when they later are used, the widget remains a text widget which is unacceptable behavior. fixed a crash on TreeButton -- any other issues can be fixed in a similar manner.
Copy link
Member

@kkoreilly kkoreilly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rcoreilly I see now that you merged this PR into #1321 already, so I will close this PR.

However, when testing this I noticed two things:

  1. The parts None button will still open a dialog, which it shouldn't.
  2. The properties map now correctly updates when switching from nil to an extant map, but it does not update when switching between two different extant maps (run the inspector in the docs and select a frame and then a text element to see this effect).

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.

3 participants