Let an unexpected warning/error escalate rather than hide it.
This commit is contained in:
parent
2f3d362240
commit
d3058f6063
1 changed files with 5 additions and 1 deletions
|
@ -459,8 +459,12 @@ public class RuffyScripter {
|
||||||
{
|
{
|
||||||
if(currentMenu!=null && currentMenu.getType()==MenuType.WARNING_OR_ERROR)
|
if(currentMenu!=null && currentMenu.getType()==MenuType.WARNING_OR_ERROR)
|
||||||
{
|
{
|
||||||
|
throw new CommandException().message("Warning/errors raised by pump, please check pump");
|
||||||
|
// since warnings and errors can occur at any time, they should be dealt with in
|
||||||
|
// a more general way, see the handleMenuUpdate callback above
|
||||||
//FIXME bad thing to do :D
|
//FIXME bad thing to do :D
|
||||||
pressCheckKey();
|
// yup, commenting this out since I don't want an occlusionn alert to hidden by this :-)
|
||||||
|
//pressCheckKey();
|
||||||
}
|
}
|
||||||
else if(currentMenu!=null && !currentMenu.getType().isMaintype())
|
else if(currentMenu!=null && !currentMenu.getType().isMaintype())
|
||||||
{
|
{
|
||||||
|
|
Loading…
Reference in a new issue