Support and General Use > User Interface and Voice
UISimulator
g-funk:
I did some more testing and it looks like my CPU problem has to do with the Iriver Sim. Im using the H120/140 version.
AlexP:
I'ver just had a look at it on my system in case it was a problem with g-funks only, but the iRiver H120/140 sim (the only one I've tried) sits at 99% CPU on mine too.
My system is an Athlon 2500+ with 1 GB of RAM, so clearly something is up!
hotwire:
--- Quote from: Mmmm on September 16, 2005, 05:22:03 PM ---Is it possible to simulate the hold button?
--- End quote ---
Sorry to resuscitate a near dead thread, but I don't suppose we could map this to the to the Scroll Lock, and just use the Scroll Lock LED on our keyboards as a hold indicator?
Edit: Through some very preliminary reading about SDL from Google, looks like the Scroll Lock key in particular may not support this, though Caps Lock and Num Lock will. Since for optimal use of some of the UISimulators (I'm personally more concerned with the gigabeat port), Num Lock should be on to allow use of the '5' key on the numpad, perhaps implement it where Hold is off when Num Lock is on. I know it's a little backwards, but we're just aspiring and off/on indicator.
Llorean:
Why not caps lock, exactly?
hotwire:
After discussing it in the IRC channel, it was suggested that Sims that have a hold button should have a hold indicator on their wps. I'm currently trying to implement it with Numpad7 and Numpad1 for DAP hold and remote hold, respectively, thereby also permitting it's use via the numpad since most of the Sim controls are through it.
Best reason why not to use caps lock, from personal experience is that I tend to multitask even when using the UISim, and if i turn caps lock on or off in another program, I can't easily predict the reaction to the UISim, and even if it is still okay, the point of the LED indicator becomes useless anyway.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version