General items related to Visual FoxPro
Andrew MacNeill has posted FoxShow #71, which includes an interview with Christophe Unrug from FoxInCloud.
I had the privilege to meet Thierry Nivelet at last years Southwest Fox conference, and I hope he’ll be back at this years conference.
Very interesting (and impressive!) stuff they’re working on.
It’s been a few days since the big announcement, and from reading the various blogs, articles and comments, it seems that half the VFP developers in the world “expected” it, and the other half were “shocked” that there will be no VFP 10.
Meanwhile, the rest of the developers in the world were “shocked” that there even was a VFP 9.
For me, while the announcement was expected, it still felt like a kick in the gut. Until I started thinking about the real surprises in the announcement. Sedna will be FREE for download and released on CodePlex under a shared source license.
The community will continue to grow and prosper. With VFPX, we have the ability to continue to further extend the capabilities of Visual FoxPro.
For me, one of the best things about using Visual FoxPro is knowing that I’m probably going to learn at least one new thing every day. The product is so rich in features, there are still many parts of the product I haven’t even touched yet. I’ll be lucky to hit them all before 2015.
So, I’m not too worried about having to learn new paradigms and new languages.
I’ve got too much unfinished business with FoxPro…
This post originally appeared at the Foxite Weblogs site.
I was working on my first VFP 9 app using Vista this week, and I had some forms that just refused to appear correctly. Specifically, the form’s Title Bar and Border would just disappear.
Looks like I’m not alone in this, as Rick Strahl wrote on his blog.
This seemed to only happen with Aero turned on, and with ‘fixed’ BorderStyle’s on my forms.
My workaround was to make the form BorderStyle=3 (Sizable), and set the MaxHeight, MinHeight, MaxWidth and MinWidth properties to the form’s Height and Width.
Problem solved!
Except for one thing. Now the user will see the ‘resize’ cursor when they hover over a border. They can try all they want to resize, but they can’t (thanks to the Max and Min settings).
I tried leaving the BorderStyle as 2, then adding code to my form’s INIT() to check the OS version and change the properties on-the-fly, but it was a no-go, so until VFP9SP2 I’m going to stick with this method for now.
This post originally appeared on the Foxite Weblogs site.
I’ve been running Windows Vista Business this week. A bit sluggish on my machine versus Windows XP, but overall I haven’t had any major issues with it.
Until today.
Today I downloaded a zipped file from the internet. It was 4.1 MB (zipped) and 10.4 MB after extraction.
What killed me was the Extraction Wizard.
The file was downloaded to my ‘personal download’ folder (on my machine, C:UsersKevin RagsdaleDownloads), and when I selected ‘Extract All’ from the pseudo-menu in Explorer, I saw the following screen:
Twenty-nine minutes to extract a 10MB file? Oh yeah, that’s how I like spending my afternoons…
Oh well, at least it has the flashy animation in the top right of the form, and (for lack of a better word) the throbbing progress bar. What the heck is it with the progress bar anyway?
After hitting cancel about 80 times, I was finally able to stop the extraction.
Then I thought, “Hmmm, I wonder how long Craig Boyd’s FLL would take?”
Here’s the answer:
Now that’s more like it.
To be fair, I should say that Windows was extracting the file to my ‘personal downloads’ folder, while Craig’s FLL was extracting the file to a different partition.
So, I decided to run Craig’s FLL again, this time extracting to the ‘personal downloads’ folder:
Freaky, huh? Took almost three times longer. I reckon Vista is doing some of that super-dee-dooper-dee-vista-is-so-secure security stuff. Maybe that is what slowed it down. Dunno.
Maybe it’s my machine. Maybe it’s my install. Maybe I’m just imagining things.
But, still, twenty-six seconds versus twenty-nine minutes?
Craig wins…
Anyone else seeing weird behavior like this in Vista?
This post originally appeared on the Foxite Weblogs site.