Create a New Forum Admin Login Member Login Contribute to Voyager Search VoyForums Help Desk VoyForums Exchange VoyForums Directory/Categories VoyForums Homepage VoyForums News FAQ - Frequently Asked Questions

[ Show ]

Support VoyForums

[ Shrink ]

VoyForums Announcement: Programming and providing support for this service has been a labor of love since 1997. We are one of the few services online who values our users' privacy, and have never sold your information. We have even fought hard to defend your privacy in legal cases; however, we've done it with almost no financial support -- paying out of pocket to continue providing the service. Due to the issues imposed on us by advertisers, we also stopped hosting most ads on the forums many years ago. We hope you appreciate our efforts.

Show your support by donating any amount. (Note: We are still technically a for-profit company, so your contribution is not tax-deductible.) PayPal Acct: Feedback:

Donate to VoyForums (PayPal):

[ Login ] [ Contact Forum Admin ] [ Main index ] [ Post a new message ] [ Search | Check update time | Archives: 1 ]

Subject: Re: Conflicts: Exclusion list? Author: Scott Dreslinski [ Next Thread | Previous Thread | Next Message | Previous Message ] Date Posted: 20:52:32 01/20/03 Mon In reply to: Temis Nunez 's message, "Conflicts: Exclusion list?" on 15:47:20 01/20/03 Mon >Hi there. I just tried the 2.0 version of Qlaunch and >it is awesome. There are problems, however, with >conflicts between Qlaunch and most games. Most games >will simply pause as soon as you press any button >assigned to Qlaunch, and will stay paused until you >let go. > >I suggest two ways of getting rid of this problem: > >1- Adding a feature to Qlaunch where we can select >from a list of present applications and activate or >deactivate Qlaunch depending on which applicaiton is >running. It should to support applications on VFS >media as well. Always the gamers... :-) You're not the first one to tell me about the interaction with games, and ask for the same solution. It is on a todo list. The VFS part is harder, because QLaunch currently does not allow you to launch VFS apps because of the complexity with having to delete the app from RAM after you exit the VFS app like the main launcher does. First round implementation may just be ram apps exclusion list. If QLaunch in the future supports launching apps from VFS, then the exclusion list could also include the VFS apps. >2- Adding a feature that would allow one to assign a >completely separate keystroke to activate or >deactivate Qlaunch altogther, say, for example, >hitting a quick sucession of certain buttons, like >[datebook]-[notepad]-[datebook]-[notepad]. I am sure >there are other unique, unobtrusive keystrokes that >could be used in this manner... I could just make it a like the other special features. Where you map it to one of the things already supported by QLaunch to quickly disable QLaunch. It may not be possible to make it a toggle where it activates or deactivates. Deactivates is easy as QLaunch is already running. But QLaunch needs to be de-activated completely to not interfere with games, so at that point, there can be no quick keystroke to enable it again as QLaunch is not active. I'll think about it some more... One thing you may want to do right now, is map QLaunch as an application to launch on one of the hardkeys. For example Longer DateBook = Launch QLaunch. Then if you want to play a game, just hold the datebk until 3 flashes, and then tap the enable checkbox to disable QLaunch. You can now play your game. Like I said, this may just be a temp solution, I'll look into the above. [ Next Thread | Previous Thread | Next Message | Previous Message ]