Skip to main content

Displaying a Progress bar that doesn't affect your program

I have been really intrigued by the MTmyVFP project on Codeplex - primarily because I want my FoxPro apps to be as efficient as possible and to run in the background where possible but one of my pet peeves in a recent application is that if I'm doing some heavy work and want to display an animation (similar to the Copy files that you see in Windows), the animation really gets bogged down with the processing.

As a result, it looks funky to the user. I had asked Claude Fox if MTmyVFP could be used to do this - and the answer was to make my processing code run in the background and then make the animation run in the main application thread.

That wasn't doable but it made me think: what if I had an application that could show the animation and then I would just call it when needed.

Here's how I did it in VFP:


oForm = .NULL.

PROCEDURE Show (tcTitle,tcAvi)

THIS.oForm = CREATEOBJECT("frmanimation",tcTitle,tcAvi)







DEFINE CLASS frmanimation AS form

Height = 106

Width = 377

ShowWindow = 2

DoCreate = .T.

AutoCenter = .T.

Caption = "Working"

ControlBox = .F.

AlwaysOnTop = .T.

Name = "frmAnimation"

LPARAMETERS tcTitle, tcFile

IF EMPTY(tcTitle)
tcTitle = ""

THIS.Caption = tcTitle
IF EMPTY(tcFile)
tcFile = "filemove.avi"
llRet = .T.
lcErr = ON("ERROR")
ON ERROR llRet = .F.
IF FILE(tcFile)
on error &lcErr

PROCEDURE AddAnimation
.Top = 3
.Left = 0
.Height = 100
.Width = 372
.Visible = .T.
LPARAMETERS nError, cMethod, nLine

** Ignore it

*-- EndDefine: frmanimation

Then build the code as an EXE. I called mine THERM.

Now, whenever you need to show a thermometer, you can call

lo = CREATEOBJECT("Therm.oani")

(hint: you can find AVI files in the VFP Home Directory under Graphics\Videos.)

Your progress bar will appear right in the middle of the screen.  Now when you need to close it, just call:


You can take this even further by changing the form details with THIS.oForm.Caption, etc, etc.

The only downside here is that you HAVE to register your EXE so you can instantiate it but you can do that easily simply by running it once with a REGSERVER.

Now, of course, there is a GOTCHA and that is that if you run this class, you may notice a weird transparent background every now and then.

The solution? Forget using a non-visual class. Instead, create a form with the same code and drop the control on it to begin with.

For good measure, set the Center property of the Animation control to .T.

Then you're even BETTER to go.

So in my class, instead of doing the CREATEOBJECT, I simply call

PROCEDURE Show (tcTitle,tcAvi)

DO FORM DispAni WITH tcTitle,tcAVI NAME THIS.oForm


The end result is a much smoother animation while your application does all its work.

Powered by ScribeFire.


Brian said…
I did something similar a while back, but I used a free table to store the progress state. In my processing application, I would simply update the values in the table, there was no need for the programs to interact.

create table status ( ;
title c(50), message c(100), ;
percent n(3,0), paused l, cancelled l ;
append blank

The progress app contained a pause button which would lock the single record table and a cancel button.
Andrew MacNeill said…
Cool idea, Brian.

In my case, I didn't want to show a Thermometer persay but rather the animation (maybe I should have changed the title of my post).

We already have a thermometer showing at the bottom of the screen which updates every 200 records.

But that's definitely a useful approach as well.
Brian said…
I was eventually planning on sticking the progress application in the system tray, never got the time to do it.

The last time I tried putting an application in the system tray (using VFP8 and Binding) it was so buggy that I ditched the idea.

I'm hoping that VFP9 has better support for this sort of thing. Alternatively, a C# or VB app that uses ODBC to read the status.dbf table would probably be easier to stick in the system tray.
Luc Nadeau said…
The Ole control seem to run unly file from disk.

I've tried to run the AVI file that were include in my Project without success.

Any tips?

Popular posts from this blog

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator)

So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinctions I…

Security in Windows 10

 discusses some Windows 10 privacy settings and their implications.

"Finally, we will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary." "In other words, Microsoft won't treat your local data with any more privacy than it treats your data on its servers and may upload your local data to its servers arbitrarily"
I did a quick install on a VM choosing the Express settings. When I fully deploy this on a real workstation, I will likely choose to wade through all of the individual pages, as David recommends.

Of course, losing one's privacy is nothing new - it's happening all over the place (despite Santa Ana's police force's lawsu…


I'm not TRYING to be "fanboy-flame bait" but what I saw yesterday was a typical "Do it this way, now do it this way and then we'll go back to this way" all over again.... a move similar to what Microsoft does to developers on an ongoing basis.

Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.

Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"

Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.

Guess that means the iPhone 8 will be back to boxy.

And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming.  The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" wor…