[APBeta] Showstopper on Windows 10

Fri Sep 1 08:58:21 PDT 2017

Correction on my problem report - I observed this issue on AP 2.3a12, the version I’m currently running.  Earlier I said I was running the latest stable release.

I’ve been experimenting with exiting and relaunching AstroPlanner with open plan documents stored on Dropbox,  but I have been unable to reproduce the issue so far.  I’ve been updating plan documents, saving them, exiting and relaunching and it seems to be behaving normally.

One possible workaround for this issue is go to Preferences > General > Opening plan documents and uncheck “Remember open documents”.

M.

> On Aug 31, 2017, at 8:07 PM, Michael Portuesi <portuesi at jotabout.com> wrote:
> 
> I DON’T use OneDrive, and I have seen the issue.  But I do use DropBox, and I’m pretty sure I’m using a DropBox folder to hold my AstroPlanner documents.
> 
> 
>> On Aug 31, 2017, at 11:23 AM, Paul Rodman <paul at ilanga.com <mailto:paul at ilanga.com>> wrote:
>> 
>> (I’m testing behind the scenes with Tim)
>> 
>> He notes that the issue might be related to having the plan documents resident on OneDrive. This seems like a smoking gun to me. Anyone seeing this issue with plan docs on OneDrive?
>> 
>> Paul R.
>> 
>>> On Aug 31, 2017, at 10:41 AM, Tim Long <Tim at tigranetworks.co.uk <mailto:Tim at tigranetworks.co.uk>> wrote:
>>> 
>>> Happy to do that Paul. Just tell me what you need.
>>>  
>>> Best regards,
>>> Tim Long
>>>  
>>> From: APBeta [mailto:apbeta-bounces at lists.astroplanner.net <mailto:apbeta-bounces at lists.astroplanner.net>] On Behalf Of Paul Rodman
>>> Sent: 31 August 2017 18:39
>>> To: AstroPlanner Beta Testers <apbeta at lists.astroplanner.net <mailto:apbeta at lists.astroplanner.net>>
>>> Subject: Re: [APBeta] Showstopper on Windows 10
>>>  
>>> If you’re willing to run a remote debugger app (I’ll provide), opening a port to the outside world, and letting me know what your IP address is, I can try uploading and running the app remotely in debug mode. Let me know and we can take this private.
>>>  
>>> Paul R.
>>>  
>>> On Aug 31, 2017, at 10:10 AM, Tim Long <Tim at tigranetworks.co.uk <mailto:Tim at tigranetworks.co.uk>> wrote:
>>>  
>>> If anyone can help me reproduce this issue on Win 10, I’m pretty sure I can track down the problem and fix it.
>>>  
>>> Very happy to help, but you will need to provide guidance on what you want me to do. Would you like me to run an instrumented build or something? I can reproduce it every time on my system, even when starting from a clean install.
>>>  
>>> My Windows version is Windows 10 Pro Insider Preview build 16728.
>>>  
>>> Best regards,
>>> Tim Long
>>>  
>>> From: APBeta [mailto:apbeta-bounces at lists.astroplanner.net <mailto:apbeta-bounces at lists.astroplanner.net>] On Behalf Of Sander Pool
>>> Sent: 31 August 2017 15:11
>>> To: AstroPlanner Beta Testers <apbeta at lists.astroplanner.net <mailto:apbeta at lists.astroplanner.net>>; Paul Rodman <paul at ilanga.com <mailto:paul at ilanga.com>>
>>> Subject: Re: [APBeta] Showstopper on Windows 10
>>>  
>>> Great news on the z order bug Paul!
>>> 
>>> Sander
>>> 
>>> On August 31, 2017 9:30:00 AM Paul Rodman <paul at ilanga.com <mailto:paul at ilanga.com>> wrote:
>>> 
>>> Very recently the Xojo boys figured out that they had the Z-order of controls backwards, explaining the terrible flickering and refreshing controls issue on Windows. I’m hoping that this will be fixed in the next major release of Xojo (a couple of months). Hard to believe it’s been like this for almost 20 years…
>>>  
>>> No, I’m not going to open source anything yet. Yes, development is going slowly since I need to make (real) money doing other stuff, but I have no plans to give up on AstroPlanner yet.
>>>  
>>> If anyone can help me reproduce this issue on Win 10, I’m pretty sure I can track down the problem and fix it.
>>>  
>>> Paul R.
>>>  
>>> On Aug 31, 2017, at 6:03 AM, Tim Long <Tim at tigranetworks.co.uk <mailto:Tim at tigranetworks.co.uk>> wrote:
>>>  
>>> It’s worth a try. At least then it’ll be possible to re-launch the app without resorting to task manager.
>>>  
>>> I guess Paul is suffering from the effect of write-once-run-anywhere frameworks. The problem with them is that if they do run, they are either suboptimal or look and feel like none of the other apps on the platform. AstroPlanner is actually pretty good in that respect – but the screen redraw issues that have plagued its entire history are a case study in the down-side of these frameworks.
>>>  
>>> Paul – don’t shoot the messenger OK, this is just a thought I’m throwing out there. I get the feeling that you are sort of giving up on AstroPlanner and in particular the Windows version. Have you considered open-sourcing it? It’s not mutually exclusive with selling licenses for money and it may be a way to get more eyes on the code which may ease the maintenance burden. Just thinking out loud.
>>>  
>>> Best regards,
>>> Tim Long
>>>  
>>> From: APBeta [mailto:apbeta-bounces at lists.astroplanner.net <mailto:apbeta-bounces at lists.astroplanner.net>] On Behalf Of Michael Portuesi
>>> Sent: 31 August 2017 13:49
>>> To: AstroPlanner Beta Testers <apbeta at lists.astroplanner.net <mailto:apbeta at lists.astroplanner.net>>
>>> Subject: Re: [APBeta] Showstopper on Windows 10
>>>  
>>> I missed the part in Tim Long’s email where he says this problem appeared with the beta build, but cleared up when he reverted to the release build.
>>>  
>>> I’m running the current release build on Windows 10 and have experienced the problem.
>>>  
>>> If I understand the proposed fix, it will definitely get the app out of its weird zombie no-window state.  But it likely means the user has to launch the app twice - the first launch resulting in the app appearing onscreen, then exiting.
>>>  
>>> If I can come up with a recipe to reproduce the issue, I will report back here.
>>>  
>>> Michael P.
>>>  
>>>  
>>> On Aug 30, 2017, at 9:40 AM, Paul Rodman <paul at ilanga.com <mailto:paul at ilanga.com>> wrote:
>>>  
>>> I’ll check (on Windows) if any windows are currently open and quit if none are. This should work to “resolve” the issue (unfortunately I can’t reproduce this).
>>>  
>>> Paul R.
>>>  
>>> On Aug 29, 2017, at 5:52 PM, Tim Long <Tim at tigranetworks.co.uk <mailto:Tim at tigranetworks.co.uk>> wrote:
>>>  
>>> In the latest beta build, I get a problem where the app usually works first time after installation, but then on the second and subsequent launches the window appears/disappears/reappears a couple of times, then it finally disappears and doesn’t come back.
>>>  
>>> It looks like the app has quit – but it hasn’t. On investigating in Task Manager, AstroPlanner will be running as a “background process” i.e. an app that has no window. Because it is already running, I can’t launch a fresh instance, and because it has no window, there is no UI so I can’t interact with it or cause it to exit. The only option is the Big Red Button (End Task or reboot).
>>>  
>>> I tried deleting everything from %AppData%\AstroPlanner and that causes the app to start as a new install, setup wizard runs, etc. and the app works fine for the first launch. But on the second launch, I am once again haunted by the headless application.
>>>  
>>> I’ve reverted back to the release build and this problem does not happen in the release build. So it looks like it is a new thing with the beta. I’m sorry I can’t give you an exact build number because I’ve reverted it but I do try to keep my beta builds up to date so it should be the current build.
>>>  
>>> Best regards,
>>> Tim Long
>>>  
>>> _______________________________________________
>>> APBeta mailing list
>>> APBeta at lists.astroplanner.net <mailto:APBeta at lists.astroplanner.net>
>>> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net <http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net>
>>>  
>>> _______________________________________________
>>> APBeta mailing list
>>> APBeta at lists.astroplanner.net <mailto:APBeta at lists.astroplanner.net>
>>> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net <http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net>
>>>  
>>> _______________________________________________
>>> APBeta mailing list
>>> APBeta at lists.astroplanner.net <mailto:APBeta%40lists.astroplanner.net>
>>> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net <http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net>
>>> _______________________________________________
>>> APBeta mailing list
>>> APBeta at lists.astroplanner.net <mailto:APBeta at lists.astroplanner.net>
>>> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net <http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net>
>>>  
>>> _______________________________________________
>>> APBeta mailing list
>>> APBeta at lists.astroplanner.net <mailto:APBeta at lists.astroplanner.net>
>>> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net <http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net>
>> _______________________________________________
>> APBeta mailing list
>> APBeta at lists.astroplanner.net <mailto:APBeta at lists.astroplanner.net>
>> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.astroplanner.net/pipermail/apbeta-astroplanner.net/attachments/20170901/9d1ee28a/attachment-0001.htm>