[domu]

Last time I checked XBMC, couple of years ago,
I found that there is no (easy) way to bail out
when you press CANCEL button. In many cases
pressing it to terminate action from script was
either not working at all or after long delay. To
make things worse there was no any indication
of the progress of action (beyond "Cancelling"),
so after pressing Cancel, one have to wait,
guessing, if it will work, or will have to power
cycle the box.

I have just installed latest build and apparently
the problem is still there.

I find it quite annoying since there are only two
choices: 1. Have to wait undefined period of time
to get the script cancelled, or 2. walk to XBOX
to hard reset it.

It seems to manifest itself most often while
attempting to cancel stream-play using MPlayer
module.

Is there any chance to have it fixed ? (either
by some sort of progress indication, preferably
with time-out function, or by forced quit (like
ABORT button or something))

Are developers aware this problem ?

Or it's just me ?

[jmarshall]

If it's a script, then it's the scripts fault for not correctly terminating. Whether or not there should be some safety "fallback" cutoff for scripts to force their termination is a different question, but has many inherent problems (terminating anything when it isn't ready to do so is problematic).

If it's within XBMC itself, then please state EXACTLY where it is. Most cases are terminated correctly. Furthermore, if it's a rogue thread (i.e. a bug), there is nothing that we can do, as you cannot kill a thread on xbox from a separate thread.

Cheers,
Jonathan

[Nuka1195]

imo, for scripts, it should be left to the scripter and the scripter should handle it properly.

but an option to hide the cancel button would be nice, there are times when cancel should not be allowed.