This reminds of the bug that was fixed 2-3 versions ago and I reported, where if you entered a value in the IDE, it didn’t save the value if the input lost focus… you had to press enter in order to have the IDE save the value.
This time… I have a custom control, it’s a container with various properties. The placeholder property (shown in the video) is a computed property and each time I open / close the project, I have to give each and every input control across the project focus so the IDE will use the value that it shows for the given property.
It’s such a major drawback as with every release we have to manually check that each and every input (hundreds!) across our (huge) project has received focus during that session, so the god damn IDE will use the value it already shows us, for the property!!!
The video demonstrates a project with a custom control
The IDE correctly shows all it’s properties and values
The input control has a property called “Placeholder” which behaves in an identical way as Xojo’s textfield “Hint” property does.
Xojo’s IDE correctly shows the value placeholder property in the IDE when you focus the control.
If I wouldn’t focus the input field, the placeholder value is not shown in runtime.
Hence… i have to go through the project, focus each and every custom input control and after I do so, Xojo correctly show’s the placeholder value.
When I close the project, the process repeates… the IDE shows the placeholder value (computed property) but unless I focus each and every custom control in the project (hundreds)…the placeholder is not shown.
The video shows how the input fields show up with no value in the runtime video, but when the project is closed → the custom control is clicked on (receives focus) and project is run again → you see the placeholder value appear. In the video I do this for 5 different input fields (first they are empty, then focused and then they show the value) = IDE bug! (And an unbearable one)
The bug is how Xojo stores custom properties for custom controls.
Have you tried using a standard Property (not a Computed Property) for your PlaceholderText?
I found some weird value behaviour in my early projects using Computed Properties for what I made available in the Inspector panel. But after changing those to regular Properties, I haven’t had a problem since. But maybe that’s just me (or an old bug that has since been fixed).
