During classes (working in a lab with Debian testing machines), I often have the problem that students push the 'Stop' button in a module GUI window, thinking that this will end the command. This can happen, for example, when they launch a raster command without having adjusted the region, leading to an enormous amount of cells and thus to very long running times.
However, pushing the button stops only the interaction between the command and the GUI, but not the underlying process. I have thus seen student with 3 v.to.rast processes running in the background which they thought they had stopped.
Could someone explain to me what the exact idea behind this stop button is and how it should work / be used ? And maybe we should think about whether it is a good idea to give the user the impression that they can actually stop the process.
2015-12-15 13:18 GMT+01:00 Moritz Lennert <mlennert@club.worldonline.be>:
However, pushing the button stops only the interaction between the command
and the GUI, but not the underlying process. I have thus seen student with 3
it should terminate underlying process, if not please fill a bugreport. Ma
2015-12-15 13:18 GMT+01:00 Moritz Lennert <mlennert@club.worldonline.be>:
However, pushing the button stops only the interaction between the command
and the GUI, but not the underlying process. I have thus seen student with 3
it should terminate underlying process, if not please fill a bugreport.
Hmmh. I just tried on my own computer with freshly checked out trunk and grass70 and with Debian's 7.0.2 and it does work. I'll have to check in the lab, again (grass 7.0.1). Maybe the specific config of the lab is the problem.