Highrez

Please extend simulated keystroke RUN command of (path to) application, the path (to file, with any extension) we use in {run:<path>} will be ran by. That is possible by command line, and I use it if I want to run some file (that is associated with its app.) by other one where it works as well, but ...

Wow, what a coincidence. I found this bug in about same minute as you :shock: I changed my delayes of HELD button for another 'Held for actions' from 0 to 0, 250ms to 333ms, 500ms to 666ms and 750ms to 999ms that initially I increased of 1ms to 1000ms. After warning I rolled it back to 999. I did no...

I just realised I posted this request even month after you released current XMBC version, so probably time to start working on next Beta is coming Anyway, when you are ready will join you in your tests again

Because I use same XMBC profile on differently named computers with differently named users where are differently named disks I can't use just {run:c:\users\specificuser\file.exe } for all computers I work on, as 'specificuser' differs for every computer. I know you bound XMBC to Windows run command...

Yes that would be nightmare, but in scenario I see you understood me unfortunately wrongly. I suggested to create 5 topics, choose 1 of them only, while 4 others lock on to be back to for next Beta's. So when you finish working on few things (features and bugs) from first one (where if needed you ca...

Maybe do that you'll create 5 topics, 1 big feature and 2 small each, plus 3 bugs to fix. So for ex. Features: - the hardest / most wanted - some other one - some other one Bugs: - 1st bug - 2nd bug - 3rd bug Choose the topic you want to focus on at the moment in first instance, depending on differe...

We talked about it few times between Beta 2 and 5. Then you made it worked, but I don't know how long as once I tested it after a fix I had no reason to check it again until recently I found by chance it doesn't work again. You can read of it in few posts on this (and another) page: Third page of XM...

Okey, so revise it when you have time.

The example of difference for both enters / returns in Photoshop:

Regular Return takes text cursor to next line, while numeric Enter applies changes.

It was introduced in this Beta the wrong way, then for my request fixed, and now again broken.

Too bad I didn't check updates today earlier. Now I did it and found a bug in no time

The numeric {RETURN} should be called {NUMENTER}. From dropdown list they work correctly. With {} both have same functionality. It is important because at least for Photoshop they are meant to work differently.

#612 works too now, if beside that you wrote you fixed also behaviour I reported 3 weeks ago: Bug 1

Regarding Enters I think you could miss my report (also from Jan 5th): Bug 2, (backspace and f.. work)

#670 works well, but if that wasn't mentioned in changes I'd like to say holding simulated keystrokes {} and pressing any of 2 Enters does not enter them to text area (that worked few Beta's ago to later got broken).

Thanks for donation to Phil

If that is not Default profile then you should untick "Only send if profile's process is active' in SimKeys.

You may also use Simulated Keystroke RUN command to run .vbs file.

No it doesn't. Use SimKeys in Button Held or describe what exactly happens.