Replies

Hey hey now!

That solution is ok. This is for personal use. I am migrating an access application to VB in preparation to migration to “another” language!

–Llyal

Thanks for the help- at least i know the problem i have might be an isolated case; this behavior only has happened a couple of times so far; I am wondering if the behavior occurs when i start an .exe project, set up some ado controls, save project, but don’t close project- as i do other things the behavior then occurs; i am thinking that if i close the project after i set up my ado controls and then re-open it, this will force the VB IDE to “flush” itself; I strongly suspect the VB IDE is not remembering its state properly;

–Llyal

Charlotte,

Thanks. A co-woorker lent me the book- I see that it does have decent information on the ADO data controls.

–Llyal

RL,

Thanks for the tip. I have found that both the SetFocus in API and VB exibit weird flickering behavior when used in a specific way with a form. I described the problem in a related post. This problem occurs on the Windows2000 platform- does not occur on WIn98 or WinNT (don’t know about other platforms);

–Llyal

It looks like I will be writing drivers from scratch! I am developing on NT/2000;

Yikes!

–Llyal

Hi,

I just want to hook up wires to the bus and read-and-write; I am going to start out simple with a switch and LED, and then build up more complex configurations; I am hoping that VB has has support for working with the computer bus;

–Llyal

Jay,

When you “permanently” install fonts, you are absolutely correct; I couldn’t install more than several hundred fonts this way;

But I have found that by using the APIs and installing the fonts temporarily, I could install 3800+ fonts and manipulate Word and other apps with no great problems; and the computer will revert itself back to the “permanently” installed fonts upons a re-boot (without having to unistall all the temp fonts);

This is an interesting workaround to a windows limitation;

Try it, you will see for yourself!

–Llyal

Kevin,

Thanks; once I learned that the keycodes were Hex values, using this API lib became a snap;

–Llyal

Jay,

Thanks for the input- it looks like getting the font name is not easy; this probably explains why I have not seen much about this on the internet;

I could be taking the wrong approach; what I could do is use Word- I could enumerate through the installed fonts in Word, remember them, install the font, then enumerate through the installed fonts again, find the “extra” font and get its name;

You can see how this will be slow for 3000+ fonts, but it is better than nothing;

Thanks for the help!

–Llyal

No; my windows 2000 set up if like a “minimal” NT box;

Don’t lose sleep over this- I have found a workaround that is good enough;

–Llyal

Geoff,

For my application, if i only set the focus once, when the focus-flickering-bonanza starts, the form becomes unfocused and remains unfocused (which is not desirable);

Don’t lose sleep over this- I have found a work around that gives me what I want without problems;

–Llyal

Geoff,

I tried your code; neither the form_LostFocus or form_GotFocus events fire eventhough the form flickers from a focused and unfocused state;

If I set Me.Setfocus when the form is unfocused, shouldn’t the form_GotFocus event fire?

Geoff, are you replicating this problem on a windows 2K SP2 machine? I have tried it on three and get the same problem; this problem does not occur on NT or Win98, so if you do it on those platforms you won’t see the problem; If you are using Win2K, and cannot verify any of my problems, then I will need to re-evaluate my situation;

Thanks for the help!

–Llyal

Charlotte,

I have a form focus problem (the details are in another post I made a few days ago under the title “Weird Form Focus Problems With the Mouse (VB6 SP5 and Windows2K)”); I want to try using the windows focus API to see if this might fix the problem; I have found that using the APIs are straightforward, but I am having problems with this Setfocus API;

Any help is appreciated,

–Llyal

Charlotte,

I checked this problem out on an NT box- I found no problem there, so this might be a problem with windows 2000; I also checked this problem out on a freshly set up machine and the flickering still persists, again pointing out the OS as the problem;

It looks like my workaround is the only way to go- not a nice solution, but it works ok.

Thanks for the help!

–Llyal

Charlotte,

I am trying to set the form focus without clicking on the form. I think that if I set the form focus in the MouseMove event, it should not matter if I set it once or many times, the form should not arbitrarily “unfocus” . Try duplicating the problem i have described and you will see: Make a blank form in VB6 and set the form MouseMove event to Me.Setfocus; Run it; Now unfocus the window by clicking on another window or a blank space on the taskbar; Now move the mouse cursor over the form. Right after the mouse cursor enters the form, the form focus state rapidly flickers on and off for 5-30+ times before stopping. This is weird behavior. My workaround is to set the form focus 20+ times in the MouseMove event to “speed through” this flickering.

To me, unless I am doing something wrong, this looks like a bug, either with the VB6 form MouseMove event or with the way Windows 2000 handles its windows.

Or am I doing something worng?

–Llyal