Interactive wrote:Didn't know if possibly there was enough demand to justify him including this as a built in feature. It would be reasonably easy, I assume, for a guy who could write an application like SDesk, to add a function that is called by one of the User remote codes....right? Assuming that SDesk was running all of the time (which, if you do use SDesk, that would most likely be your intention anyway), then it could actually just work from within the app.
Ah, I see. No, that makes sense. And your macros sound like how I'd do it.
I haven't seen Sven around for a couple of months, but you could always email him I guess.
There is already in SDesk something very much like this
Code: Select all
%custominfo
%customrotate
%customff
%customfb
the file name of the scripts that will be invoked for the respective
remote button (while inside SDesk).
So, for example you could map the rotate button to macro 1, and info to macro 2. (not ideal of course). All that would be needed would be for SDesk to support the remote 'user defined' keys.