[rkward-tracker] [ rkward-Feature Requests-1184757 ] interupting commands

SourceForge.net noreply at sourceforge.net
Sun Apr 17 17:59:50 UTC 2005


Feature Requests item #1184757, was opened at 2005-04-17 19:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=459010&aid=1184757&group_id=50231

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Thomas Friedrichsmeier (tfry)
Assigned to: Nobody/Anonymous (nobody)
Summary: interupting commands

Initial Comment:
Interupting commands is broken. But also it  
never was quite good, you could only ever  
interupt the one command last submitted in the 
console (as far as I remember that is). 
Hence instead of "fixing" this, it will probably 
make sense to come up with a better solution. 
After all, it should also be possible, to interupt a 
command from a plugin, from a command file, 
etc. (while generally internal commands might 
not be safely interruptable). 
What I think would be cool is to have a widget 
display a list of commands currently in the 
execution stack, i.e. pretty much visualize the 
RCommandStacks. Then commands / 
command chains can be selected to be 
interupted, and also we can make a cool 
screenshot ;-). 
What may make this somewhat non-trivial is the 
threading stuff involved. Not sure right now, 
whether we can safely get at the data in the 
RCommandStacks from the GUI-thread without 
duplicating that data. I'll look into that later and 
add a further comment then. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=459010&aid=1184757&group_id=50231




More information about the rkward-tracker mailing list