SRL Archive - Suggestions

…like Ctrl-Alt-A and Ctrl-Alt-S in SCAR would be nice. Maybe Simba has it already but its not in the menu and I Is Simba Noob. Thanks :D

Yeah, we need global keybindings for Simba. Currently they only work when Simba is selected, but I think Stop Script should have a global one. Mind you, Simba can run several scripts at once so this can be tricky.

From: Wizzup?
Yeah, we need global keybindings for Simba. Currently they only work when Simba is selected, but I think Stop Script should have a global one. Mind you, Simba can run several scripts at once so this can be tricky.

Like CTRL + S to select stop mode, then the next numeral to be pressed (1,2,3…) will select what script to be stopped?

EDIT: Ofcourse every other key if pressed would terminate the stop mode.

I think the script should handle it really. I mean, everyone wants a forever running script but it should be able to safely finish when needed, which should include testing. Having a procedure or the like run when the script terminates always seemed quite silly as me - seems it should be more for emergency stops because something crashed rather than to handle general housekeeping stuff.

Anyway, that's just me. Given Simba's flexibility in what can be targeted and collect input from etc it would probably need support for detecting the actual keyboard as opposed to simulated interface of something else or maybe not. I'm probably just rambling now.

From: Wizzup?
Yeah, we need global keybindings for Simba. Currently they only work when Simba is selected, but I think Stop Script should have a global one. Mind you, Simba can run several scripts at once so this can be tricky.

Probably have Simba only stop the script whose tab is currently open. I mean usually when you're scripting or debugging and wanna press stop you only want the script that you're working on to stop.

From: mixster
I think the script should handle it really. I mean, everyone wants a forever running script but it should be able to safely finish when needed, which should include testing. Having a procedure or the like run when the script terminates always seemed quite silly as me - seems it should be more for emergency stops because something crashed rather than to handle general housekeeping stuff.

Anyway, that's just me. Given Simba's flexibility in what can be targeted and collect input from etc it would probably need support for detecting the actual keyboard as opposed to simulated interface of something else or maybe not. I'm probably just rambling now.

Well, when I'm macroing a flash game I usually don't outspeed Simba in the MoveMouse calls with my own mouse, so it can be quite annoying. ;)

From: ZephyrsFury
Probably have Simba only stop the script whose tab is currently open. I mean usually when you're scripting or debugging and wanna press stop you only want the script that you're working on to stop.

Yes, but I think we also need one to kill all.

If I produce a script that I know I'll likely need to stop, I usually put in an "if IsKeyDown('q') then TerminateScript" or break or the like. I can see why people would want to have an instant method of stopping, but I still think a script engineered to handle user input during runtime, including stopping the script, would be a better thing to push as it encourages some good scripting practices and the like. Or maybe not, I know I can be wrong.

From: mixster
If I produce a script that I know I'll likely need to stop, I usually put in an "if IsKeyDown('q') then TerminateScript" or break or the like. I can see why people would want to have an instant method of stopping, but I still think a script engineered to handle user input during runtime, including stopping the script, would be a better thing to push as it encourages some good scripting practices and the like. Or maybe not, I know I can be wrong.

I agree with mixster. I always add manual emergency breaks and stuff to make sure I don't get one of those moments where SCAR takes control of your comp and you can't do a thing

I don't know howto add a global shortcut… Only way I can think of is having a thread constantly checking what keys are down and then reacting to certain combinations.. Sounds like a silly way.

From: Frement
Like CTRL + S to select stop mode, then the next numeral to be pressed (1,2,3…) will select what script to be stopped?

EDIT: Ofcourse every other key if pressed would terminate the stop mode.

Sounds perfect.

How about something like Super+Shift+1 (1 being the first tab), or maybe the number pad? It would be hard to decide on things for it, since Alt+, Ctrl+, and Ctrl+Alt are taken by many programs, and Windows uses Alt+Shift or Ctrl+Shift to change keyboard layouts if you have that enabled (depending on user settings)

:p Why not just keep it simple and only do it for the current tab? ;) That'd add only one or two keystrokes (or mouse clicks) to get to a different tab if you want to stop a different one. I think it'd work just fine.

As explained above the issue is not the shortcuts itself, but rather how to make a global shortcut….

Oh, Raymond, I wasn't saying that my post would solve the problem or anything, I was more responding to the people saying like.. shift s 1-9 for tab numbers.. It seems pointless.

From: i luffs yeww
Oh, Raymond, I wasn't saying that my post would solve the problem or anything, I was more responding to the people saying like.. shift s 1-9 for tab numbers.. It seems pointless.

I know ;-). I'm just desperate for a solution :(

Well, isn't the whole point of the new structuring of the IOManager and stuffs so that you can easily have some thing target one thing for searching, while still clicking on something and sending other input to a third thing, or something along those lines?

If so, why not make a Simba one that just targets the keyboard? The only thing I can think of is it maybe stealing input if a script wanted to target the keyboard too, but I would say that isn't a problem as you all are awesome and wouldn't let that happen.

From: mixster
Well, isn't the whole point of the new structuring of the IOManager and stuffs so that you can easily have some thing target one thing for searching, while still clicking on something and sending other input to a third thing, or something along those lines?

If so, why not make a Simba one that just targets the keyboard? The only thing I can think of is it maybe stealing input if a script wanted to target the keyboard too, but I would say that isn't a problem as you all are awesome and wouldn't let that happen.

So you're saying we should create a separate thread just for checking if a key is pressed, and if so if it is a global shortcut?

It does indeed seem a bit wasteful, but I can't think of another way. Maybe also allow the user to access it in some way so they can assign global shortcuts on a script basis?

How did freddy do it?

From: Zyt3x
How did freddy do it?

Probably some windows API -> http://msdn.microsoft.com/en-us/library/ms646309%28VS.85%29.aspx

For X11 use XGrabKey.

This is implemented for Simba on Windows.