explainOriginally Posted by 0l33l
Check for directx or opengl.Originally Posted by frodobaggins
explainOriginally Posted by 0l33l
[H]4 Life
My next generation Front End is right on schedule.
It will be done sometime in the next generation.
I'm a lesbian too.
I am for hire!
Well, if someone launches a game, then they are probably going to be using either directx or opengl. If you check if those are running, then you can disable the service for a while.Originally Posted by frodobaggins
But what if the user launches an app that uses opengl/directx but doesn't use the joystick?Originally Posted by 0l33l
AMD XP 2600+/512MB RAM/120GB hard drive
Opus 150W/DVD/GPS/7" Lilliput TS/802.11g/Bluetooth
Installed.
-GPSSecure- - GPS Tracking
-AltTabber2.2.2- - Handy touchscreen utility.
Ummm... I dunno.Originally Posted by xBrady
My idea is to have the service spy on what apps are open, and if an app matches one of the list then then joysticks won't be intercepted.
well, my app uses directX![]()
[H]4 Life
My next generation Front End is right on schedule.
It will be done sometime in the next generation.
I'm a lesbian too.
I am for hire!
Ok... there goes that ideaOriginally Posted by frodobaggins
![]()
What list would you be referring to? I don't think he could come up with every possible app that would be using opengl/directx. Wouldn't he also need the exact title bar name if he were going to call the FindWindow API function? I don't think matching to a list would work well enough.Originally Posted by 0l33l
I mean the user makes a list of what apps are going to be using THE JOYSTICK. So say you launch MAME, then Frodo stops monitoring the joystick port until MAME has been terminated.Originally Posted by ImInSanDiego
BTW: Put a space somewere in your vehicle title.
That sounds like a good idea to me. Should work very well.Originally Posted by 0l33l
BTW: Didn't realize what my vehicle title was doing...looks like our 9 fingered admin fixed it
Bookmarks