https://bugs.documentfoundation.org/show_bug.cgi?id=174295
--- Comment #11 from Jean-Pierre Ledure <[email protected]> --- I observed the same behavior of your application as you describe above. I say "of your application": it seems having a few bugs. I also admit that debugging Basic code between a dialog.Execute() and its closure is not easy: the execution hangs on the execute() statement and a new run starts when events are triggered (buttons, etc.). This is why an error occurring after an event is announced only after the execute() is finished. You can switch off any ScriptForge error handling by inserting somewhere (in Main() f.i.) next statement SF_Utils._ErrorHandling(False) I found this way two distinct errors by "playing" with your app. When those errors occur, the execution of the event stops, but the Execute() continues, what can explain multiple clicks before a normal run. 1) Object variable not set - in DialogValues_doSave() - on statement oSupplier.setValue(oVValue.V_Name, oVValue.V_Value) (two lines before the End Sub) 2) Index out of array range - in DialogMain_DoChange() - on statement oVValue.V_Name = oCtrl.Value(0) when there are no variables in the table So, IMHO, there is no evidence that correcting code inside ScriptForge would solve your issue. -- You are receiving this mail because: You are the assignee for the bug.
