Is This a Timer Issue?

Panorama X Beta 10.2
41

Ok, I was able to achieve this. Sorry, but it requires the use of secret windows. The timer code needs to follow this template:

opensecret "Path/Database Name"
setactivedatabase "Database Name"
... DO
... YOUR
... THING
save
setactivedatabase "Database Name"  // required after save
closefile

In my tests this works in all situations, whether the screen sharing is open or not. You won’t need to use bringpanoramaforward, and you don’t have to stop and restart the timer.

For the code you’ve posted, changing to this template should be easy. I’m guessing that this isn’t your real code, and that your real code may take a significant amount of work to convert to this. Sorry.

A couple of other notes about your code. First, super minor - the SelectAll isn’t doing a thing but consuming processor cycles.

More importantly, showvariables doesn’t work the way you think it does, so your monitor form isn’t going to update promptly. You are using it with a global variable, but it’s really only supposed to work with a fileglobal variable. At any rate, it will only work with the current database. I guess you are displaying gvStatus in a database called Monitor. In that case, you would need to use setactivedatabase "Monitor" before each time you use showvariables. Since you are doing this multiple times I would probably make a subroutine to do this.

gvStatus = parameter(1)+" @ "+ timepattern(Now(),"hh:mm am/pm")+cr()+arrayrange(gvStatus,1,100,¶)
let wasDatabase = info("databasename")
setactivedatabase "Monitor"
showvariables gvStatus
setactivedatabase wasDatabase
return

Then you can just call it like this:

farcall "Monitor","UpdateStatus","Timer Started"

To bang an almost ten year old drum, Panorama X is not Panorama 6. Panorama X is much more tightly integrated into the operating system. Before OS X, developers had to implement all document handling (open, save, close, etc) themselves. In a properly written OS X/macOS application, this is done by Apple’s code. This has tons of benefits, but it also means the details are not in the developers control. There’s some sort of weird interaction between document handling and screen sharing (which is also implemented by Apple). There’s nothing I can do about it, and I’m sure Apple couldn’t care less. Anyway, there is probably no other application that would even allow this sort of automation of opening/saving/closing documents in an unattended machine, so not really on Apple’s radar.

The good news is that what you want to do is achievable, though perhaps with more work on your part than you were hoping for.

42

The work is no issue and the code is organized enough that I can probably make the conversion within a reasonable amount of time.

Thanks for looking it over and offering your solution. I’ll surely let you know how it goes.

43

Among the many reasons that PanoramaX remains such an awesome tool across the board. I’ve even used it in place of Keynote and Powerpoint since it gave me so much more control for my photo presentations.

44

Thanks :grinning:. My point, however, was that Apple probably doesn’t test that this works, or even care.