on my actual project i have a custom DesktopTextField named “alemac_desktopTextField”
As you can see, it’s on a window. the “super” is set.
the options on behavior appears and are also set.
and on property list behaviors, it appears.
This naming convention wasn’t my decision. You cannot name methods or properties in this manner through standard means. It may not even be the problem, I’m just making a suggestion based on my knowledge of the framework.
You could very easily test to prove whether this theory is the cause or not.
These naming rules apply to variable and constant names,
but also apply to the name of everything in Xojo including methods,
modules and classes which you will learn about later.
Names must start with an ASCII letter (A-Z) or (a-z)
Names that start with an underscore are not recommended and not supported
so may not work in future versions
The remainder of the name can contain any of the following:
Alphanumeric ASCII characters (A-Z, a-z, 0-9)
Underscore (_)
Any Unicode character with code point greater than 127
Names can be any length
Names are case-insensitive (age and Age are considered the same)
If you use an invalid character, you will get a compile error (usually reported as a Syntax Error) when you try to run the project. For names that are specified using the Inspector, you will get a prompt indicating that the name is invalid and the name will revert to its previous name.
Ah, I bet the IDE doesn’t prevent that on those titles, but it should. Things with underscores are automagically hidden by the property inspector because they’re considered “internal”. Remove that or replace with something else and it should work just fine.
Remember, you can use just about any UTF8 character, just not underscores, spaces or operators. An em-dash would work though. —