|
-
Jan 14th, 2023, 11:29 AM
#32
Re: LED.OCX & Windows 11 Pro
 Originally Posted by daveyk021
Elroy,
I have been using your LEDUSerControl with success these last few months, but it can be somewhat delicate to changes in the VB6 IDE environment.
By that I mean, that it seems if I add another ActiveX control, i.e., "Microsoft Windows Common Controls 6.0 (SP6)", the LEDs go away and turn in to to just hash marks on the forms.
Any idea how to restore them? It is a LOT of work on some of my forms to re-add them again. Yep, they can be re-added, but the existing LEDS are gone.
Thanks much,
Dave
Dave, that's a problem with any/all custom user controls. There are a couple of solutions: 1) compile the LED UC into its own OCX file, and then pull that into your project via components; or 2) while developing just be sure to not open the actual UCs windows in the IDE, not its form designer window nor its code window. If you don't open the UC's windows, you shouldn't have that problem.
ADDED: On that last point, if you need to open the UC's windows, just be sure any form that's using the UC is closed first in the IDE. And, when you're done doing whatever to the UC, be sure to close its windows before opening any form that's using it. Taking that approach usually circumvents any problems like you describe. I suspect that those of us who make regular use of UCs have just learned these habits.
Any software I post in these forums written by me is provided "AS IS" without warranty of any kind, expressed or implied, and permission is hereby granted, free of charge and without restriction, to any person obtaining a copy. To all, peace and happiness.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|