forums.silverfrost.com

DanRRight · Posted: Mon May 18, 2015 12:45 pm Post subject: Is this my computer fault?

If this code run as is the progress bar stops in the middle. If run via debugger it works fine to the end

LitusSaxonicum · Posted: Mon May 18, 2015 1:36 pm Post subject:

No, mine runs it right through. (AMD Phenom II, 16Gb)

Eddie

Smib · Joined: 26 Apr 2009 Posts: 22 Location: Melbourne

ok for me too! - Win 8.1/intel i5 - 4570

Brian

DanRRight · Posted: Tue May 19, 2015 11:01 am Post subject:

Thanks, so i went to reboot computer and the bug is gone.
What may cause this?

JohnCampbell · Joined: 16 Feb 2006 Posts: 2554 Location: Sydney

Dan,
I can't see any error, but I simplified your stepping test.

DanRRight · Posted: Thu May 21, 2015 2:05 pm Post subject:

There was no source error but some corruption somewhere in OS or in the compiler which turned FTN95 into the insane state. Do you sometimes feel something wrong after very long period of time not rebooting computer? In DOS times that was a norm, right now this happen ones per year of heavy use.

wahorger · Joined: 13 Oct 2014 Posts: 1217 Location: Morrison, CO, USA

I've also seen the bar stop updating. And I have a way around it that worked for me. BTW, in my case, the bar stopped updating, but the underlying code ran to completion.

In my case, if I prevent the updates from occurring too fast (i.e. increase the time between successive calls), the bar works perfectly. I always call the routine, but look at the elapsed time between subsequent calls, and ignore updating the window too quickly.

In my case, I update every second (a convenient value for my application). Also, for my application, I close the status bar window at the end of it usefulness, so I know the code is still running through to the end, regardless of what the bar status actually says.

I have run across other cases where, if you do things too fast, the ClearWin+ functions don't have enough time to "clean up" from the previous call, and it can cause a crash.

I've included the code I use here. The first call (NCUR=0) initializes the window, and NCUR=-1 to close it. YMMV.