Closing a Panorama X database on Big Sur after running some procedure randomly quits Panorama X with a message that is sent to Apple automatically that starts with:
Same here, but on my computer, all need to get a repeatable crash is to open up my expense file, hit “return” to create a new record and then quit Panorama. The crash screen comes up every time after the quit. When I reopen the file, the new record has been dutifully saved though… so that makes it more of a jump scare with no importance.
i’m getting lots of crashes under big sur, not after i quit, just any time. no catastrophic data loss yet, but it is annoying, and happening way more than it should.
It have the impression that Panorama X 10.2.0.b12 crashes more often than Panorama X 10.1.2 and not just when quitting but that is difficult to quantify.
I was hoping those crashes would be fixed in 10.2 but maybe so when it is officially released. Can you tell me if the frozen highlighted cell in the data sheet bug (from Panorama 10.1 on Big Sur) is fixed in the 10.2 Beta? I just update my system to Big Sur 11.2 and Panorama 10.1 still has frozen highlighted cells in the data sheet and still crashes on quitting if I’ve made any changes to the the database.
I installed the latest beta version of Panorama X 10.2 today and I still experience frequent crashes when closing a database but almost never with any loss of data. The highlighted cell only moves with the up and down arrows but not with the left and right arrows. That makes data entry tricky but Panorama X has a wonderful undo capability if in case you enter data in the wrong field.
What macOS version are you using? My guess is that you must be running macOS 11 Big Sur because Panorama X 10.1 was working just fine on macOS 10.15 Catalina and Panorama X 10.1 and 10.2 have the same problems on macOS 11.1 and 11.2 Big Sur.
I’m having quite a few during the design process on the latest beta; they all happen in graphics mode when I’m tinkering with item placement on a form. I can make 4 or 5 (not sure about these numbers, will start keeping track) but the next one invariably causes a crash.
Yep, after 6 years on a Macbook Air mostly, I figured I’d better be prepared and got a new one. Opening DB with latest BigSur gives error message, including something about trial period – can send screen shot. Get post file close “unexpectedly quit” message. Have also been able to do a couple things, but haven’t tried any of my sophisticated operations. Running PanX 10.1.2 (2854)
I was just working on a file that has had all sorts of problems all along, and it is not getting any better. It just crashed Panorama again, and then crashed it again when I reopen and tried to open another file. I sent it to Jim some time ago. I have been trying to reconstruct it, but there are several complex things in the file, and it takes more work than I have been able to put into it. Graphics are particularly troublesome, but may not be the only thing that causes crashes, probably with some sort of memory corruption, which does not get flushed after a crash. It could be that Panorama is writing something, perhaps to the Restore and Revert cache, that is not working correctly.
Constantly crashing with Big Sur. Hope the new upgrade comes out soon! I really am disappointed with Pan X. I was one of the very early Panorama software (1980s) and loved the quality and ease of use. Not so now.
I get a crash every time (unexpected!? NO, expected every time now.) This is a BS (Big Sur) problem, because PanX was working fine under my last system, located somewhere cool in California, but not Catalina or Lompoc.
Question: Should I “report to Apple” (All Praise to It That Sustains Us) every time, or is that just a waste of time?