Don’t know how much help you’ll get with this here. I can’t think of anything that would cause the compiler to behave this way from a project source perspective. Best bet would be to open an Issues case and submit a project that reproduces the error. If you can’t reproduce the issue in a minimal project, you can make the case private.
I’m wondering if you’re using any structures. I’ve seen those render weird in the past.
I can open and run a previous version of the project which is not much different without a crash but not sure what the actual differences in code are. Also not sure how best to check given the very large number of locations containing code, is there an easy way to do a project-wide diff in Xojo?
If you use source control, IE: git, (which you should be), you should be able to view a diff of the project, assuming you’re not using the binary project format (which you shouldn’t). Could more easily pinpoint the change that way.
yeah… I had been using an xml version but sometime previously I unconsciously saved as binary (must have been a default choice or something).
Guess I’m out of luck and will have to manually check…
Yeah, that’s not fun. Please be sure to post the Issues case link here once you create one. I’m interested in what’s causing the renderer to freak out.
It was a restore from a crash - I did a ‘save as’ and must have unthinkingly just gone with whatever it served up.
Since I didn’t have this on my GitHub I just ignored that but now I obviously regret this and will export the immediately previous working version to my GitHub.
Launch the IDE from a terminal window and then open and build your project. You may get more information in there. Just type the word “open” followed by a space and then drag and drop the Xojo.app bundle onto the terminal window.
I copied a return character (Char 13) and pasted it into the application identifier field and hit build.
And I may suggest you start using version control with e.g. GIT, so while you work on a webpage and then save it, you may see that you accidentally broke something in a different module. This way you could easily prevent or reverse.