People come here with many problem and get many solutions. Which solution is the correct solution? Any one that works! Well I had a problem and now I don't thanks to JohnH (exept for the troll with the overblown ego). My gauge is working well inside .NET and my project is coming along just...
Ok Herman, here are a couple of facts for you. Windows 10 registered prjGauge.ocx. Visual Studio 2019 added prjGauge.ocx to the .NET component list. That makes prjGauge.ocx a valid .NET component. Not a dead component, but a component currently supported in .NET. Who is right? You or .NET?
Herman you shouldn't really be telling me which controls I should be using in .NET!!! You sound like a troll. I am modelling the tuning circuits of vintage radios wich use vintage air variable capacitors. The prjGauge.ocx does this perfectly. Like the vintage capacitors it has a 180 degree...
I am not experienced enough to fully understand what you wrote about "accessor members" but I am intuitive enough to play around with Let_Max and Get_Max. Get_max was accepted but Let_Max wasn't. So I tried Set_Max and it worked! Thanks, you have helped me enormously. This had me stumped and...
I have an OCX gauge control I used successfully in VB6 (prjGauge.ocx). This gauge has max and min properties that can be set by the user, like, "gauge1.max = 100". Since then I have moved to VB.Net and when I add the contol to a form it has no max and min properties. Or maybe I don't know how...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.