I’m trying to test an existing app written with Xojo2021r3.1 on macOS Sequoia but get errors from the Remote Debugger Destop.
Xojo IDE runs Xojo2021r3.1 on macOS Monterey (12.7.6)
Remote Debugger Desktop (2.5) runs on a Parallels Desktop VM macOS Sequoia (15.0), fresh install
When starting the remote debugger:
in the IDE the app is compiled and transferred normally
on the target system:
. the application is transferred and decompressed
. the application is starting (bumping in the dock)
. then I get ‘Cannot connect to the debugger (since we could not locate the target IDE to start a debug session …)’
the IDE keeps saying ‘launching application’
It’s possible this is fixed in newer Xojo versions (see #81107) but I’m not able to test as I have thousands of errors (thanks API 2 !) and do not wish update everything.
Is there any solution or workaround for Xojo 2021r3.1 ?
I could see you having “thousands of warnings” but not “thousands of errors”. The newer IDEs should be able to just build/run your app without any issues. Just don’t do “Check Project” or if you need to, go to Project > Analysis Warnings and uncheck “Show API 2 Desktop control deprecations”, “Item 1 is deprecated” and “item1 is deprecated. You should use item2 instead”.
Try to locate the app in the remote Mac and, once the error message appears, double clic in the xxx.debug app in the remote machine in order to start de debugger connection.
Unfortunately, I’m speaking of errors, not warnings. I can’t compile.
Most (all?) of them are for Einhugur ‘Custom Butons’ and ‘DateControl’.
Like
ccRequestEdit.dtReq.ValueChanged Declaration
dtReq on ccRequestEdit implements the event “ValueChanged,” but its superclass myDateControl has already implemented the event.
Sub ValueChanged()
Project > Analysis Warnings and uncheck “Show API 2 Desktop control deprecations”, “Item 1 is deprecated” and “item1 is deprecated. You should use item2 instead”.
I’ve just checked and all Einhugur plugins are from the latest version in 2021r3.1.
But you made me check, the Einughur plugins were not present in 2024r2.1 !
So the error messages are really misleading, as they don’t say the super class ‘DateControl’ do not exist but ‘its superclass myDateControl has already implemented the event.’
Adding the plugins makes the errors vanish and I’m able to remote debug on Sequoia using 2024r2.1.
Unfortunately, as stated in my first message, I’m still unable to remote debug on 2021r3.1.
I don’t have the 2024 license and do not wish to upgrade just for the remote debugger and still hope there’s a workaround. Coding in one version and debugging in an other is not confortable.
Maybe I should have make profit of the August discount ;-(
Hi Björn,
Thanks for following up. I’m aware of this.
My issue was that Einhugur plugins were not installed on 2024r2.1 but the error message was ‘its superclass myDateControl has already implemented the event.’ instead of ’ the superclass does not exist’.
In fact the super exists, but the super-super (DateControl) doesn’t.
IIRC with plugin controls, there’s another layer of supers that are not visible to users, the framework classes that the plugin controls subclass from. It’s those classes that the IDE is referring to as having already implemented the event. The IDE could probably be smarter here but it’s simply looking for exposed event definitions on the class. If it doesn’t find them, it assumes that the class implemented the events.
