Open abrudz opened 5 years ago
This may require amending the protocol, as I see no option to add output without showing the window.
Yes, either protocol change or the interpreter simply could omit posting the message if user turns of the feature.
In the IDE, the message is still written if auto-status is off, but the window isn't shown, so the user can manually go and inspect what happened. Anyway, I suggest adding show: false
I've raised issue 17116 for the interpreter side of things.
I suggest that the interpreter has no business telling RIDE whether to show the status window. That should be a RIDE preference.
That should be a RIDE preference.
Sure, but at the moment the developer can suppress the window using the I-beam. I don't know where to draw the line, but at the moment RIDE isn't notified of this. We could add a preference in RIDE, set a sensible default (off?) and ignore the I-beam?
@jayfoad No, the interpreter is not telling RIDE to show the window or not, it is just telling RIDE what the current interpreter status (the one set with an I-beam) is. RIDE (or whatever is at the other end of the line) can of course do whatever it wants with that information.
Describe the issue you are having
2036⌶0
turns off "Autostatus", that is, popping up the status window when text is written to it. RIDE seems to ignore that.startup.dyalog, the "boot-loader" for Link, relies on this behaviour.
Did you connect to an already running interpreter or start the interpreter from RIDE?
Start an interpreter
How do you reproduce the issue?
Paste the contents of Help → About (Shift+F1)