2019r3.1 difficulties

I’ve just had the situation occur where my project, which I have worked on for months in 2018r1.1, stopped working under 2019r3.1.
I was running it earlier today. At one stage it crashed OSX (apparently). Then got to the point where it would not display the main window. The icon would appear on the bar at bottom of screen, it would bounce for a bit, then stop bouncing as if the app was running. But no form. I tried putting a break point into the App.Open event, and main window .Open event…nothing.

My code has a lot of deprecated stuff in it (eg Date etc), and perhaps that is part of the problem. Though common practice with deprecation is not to break the old code, so I would assume this would work, at least since the deprecation is recent.

I have been using the 2018 version, well, since 2018. And it works very well. I mean, thousands upon thousands of hours of use. With the 2019 versions I’ve tried, they were bombing within an hour or so. I am surprised there isn’t more information about it. Or maybe I’m not looking in the right place.

I went back to 2018r1.1, it still didn’t work. So I made a new project, and dragged all the code into it. After some mucking about, I’ve got it running again.

My OS version is old: 10.11.6. Maybe that’s why?

Any thoughts on the matter? Is it my OS version, use of deprecated features…or?

[quote=473407:@Tom Dowad]My code has a lot of deprecated stuff in it (eg Date etc), and perhaps that is part of the problem. Though common practice with deprecation is not to break the old code, so I would assume this would work, at least since the deprecation is recent.
[/quote]
Welcome to API 2.0.

Unless you’re starting a project from scratch, many of us would urge you to hold at 2019r1.1.

I know that may sound somewhat harsh, but API 2.0 was a very unwelcome change for many of us who use Xojo in a commercial realm.

No idea what could cause this as 2019r3.1 works just fine for me. Maybe you should start by deleting cache files. You can ignore any warnings about API 2.0, especially if you aren’t using it anyway; deprecated stuff still works.

That sounds like project corruption and has nothing to do with API 2.0.

It might be the Captain. That one is really old now.

or copy your project and remove parts of your app until it works and then you can care the reason.

I’m running the latest 2019r3.1 and have kept my code using the old notation and have not had any false-starts or bombs. I’m using Catalina. My Xojo app on Windows was acting weird one day (fonts went tiny on certain fields, no modal dialog boxes), but a restart of Windows fixed that (I almost never restart Windows 10).

Something is haywire with my system no doubt.

Having moved everything over to a new project, and got it running again, then deleted 2019r3.1, did all my compiling and running with my good ol’ 2018r1.1…its happened again. That is, when I run the program, put a break point at the entry point…nothing. Doesn’t break, acts like its starting up, then no window. There is an icon indicating it is working. Stop and pause do not work.

Ya I had accidentally run that corrupted project again. That then caused my computer to get into a state. The MBP wouldn’t shut down properly. After a reboot things were good again. So I am attributing all of this to that same corrupted project that caused it the other day.
All nonsense apparently. I think its time for a new MBP. Too bad, this one has been very good to me.

Sometimes a good Xojo cache clearing and computer reboot can ‘fix’ some very odd bugs.

I had one yesterday, but this was a hardware bug (IMHO) yesterday.

I reboot many times, I even boot on a different OS version.

No way.

I decided to remove the DVB USB key and watch some old scifi. Two hours later, I left High Sierra and went back to El Capitan (after I reconnect the USB Key): during the boot, I took a glass of fresh water (then forgot about the bug) and was surprised to get the TV back !

So, anything can help, even the most strange or unusual :wink: