That’s true, but it’s not my issue, I’m afraid.
In normal circumstances, Xojo reports a valid location and the offending line, highlighting the class/call that makes the problem. Double-clicking the error reveals the error in the IDE.
Here, the location is empty and there’s no line mentioned; Double-clicking doesn’t do anything.
I’m still thinking the project file is corrupted. Two days ago, my code worked fine; any item needed to be excluded was marked as non-console safe (unchecking the checkboxes for individual classes). ProjectItemsToIncludeAtAll was not used at all.
And yesterday, I made changes and realized it wouldn’t build anymore. Even by reverting to the state of yesterday, by deleting my changes, the issue remains.
These steps also make me thinking the project is corrupted:
I remove the Worker and the project builds fine.
Then, I add a dummy Worker and a dummy class (CTest). In the worker, I set ProjectItemsToInclude to “CTest” and nothing more. At this point, the project can’t be built anymore, even the worker having only CTest included and no other code.
Well, I have no clue as to what those items are, except than checking the whole project, since the compiler fails to target the part of code that makes the problem.
Yes, you may even make a complex project only by debugging, thinking it works, and when you finally decide to build, you realize the core of your project can’t work.