I opened an older project (RS2012R2.1) which has a module Module1 with
TF1 <- subclass of TextField
TF2 <- subclass of TF1
TF3 <- subclass of TF2
in Xojo 2015 R3.3. I add a textfield to my window but I can’t set the TextField to TF1 or TF2.
Clicking on the pencil beside super only shows TextField, not the subclasses.
To investigate I create a new project. To make it work I have to add Module1. like this
TF1 <- subclass of TextField
TF2 <- subclass of Module1.TF1
TF3 <- subclass of Module1.TF2
This works.
HOWEVER adding Module1. to the super in the older project does not work. The subclasses simply refuse to “change” their super. Clicking on the pencil only shows TextField, none of the subclasses.
So in the older project it is impossible to set a TextField to the subclass TF1 or TF2.
The problem has something to do with modules not “using” their own scope. I’ve had similar issues. Not sure if there is a bug report on this yet. Does adding a “using” clause to the module, referencing itself, fix the issue?
I presume it still works to type the super in rather than selecting it from the dropdown. If it doesn’t, then that is a serious bug. Otherwise, it’s a less serious bug. Have you submitted a feedback report?
Try deleting the Super field (Select all content, press Delete). Then click the pencil. That will enable you to select whatever you want.
Don’t be alarmed to see the control disappear while it has no Super. It will appear as object at the bottom of the window, like a Timer would. It will come back when you select a new one.
I just created a project in RB latest release with your setup (Module with TextField subclass, subclass thereof and subclass of the latter) and opened it in the most recent Xojo version and it worked (the TextField subclass hierarchy is shown in the “Select Super” dialog. Btw this is a silly title, Xojo Inc., it should say “Select Class”, not “Select Super”.
Another thing you could try: Add one instance more to the window (in Xojo, not in RB) and see if this one works.