-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default launch configuration #52
Comments
Hi! It's great you find the plugin useful. I think setting the default to vsc's
is equivalent to
and Regarding Qt, quoting from the help "plotting with qt or other plot frameworks might require you to add an infinite loop at the end of the program being debugged. For example: |
Check version v0.4.18, and reopen this issue if it doesn't work for you. Thanks. |
I've verified this and indeed, As a side note, I've dug into handling background-opened plots a bit and it seems that a much better solution is to add a h = figure();
plot();
% ...
waitfor(h); With this the plot windows are fully responsive! I.e. I can resize the window and the plot redraws, I can zoom in etc. AND I don't use the not-so-beautiful infinite loop ;) Note: only one |
I tried it and I like that solution. I've added it to the readme.md for other folks to hopefully also get to know about it. Thanks for sharing. I still didn't test it with complex qt UI. But it's good to have several options. 🙂 |
Hi,
first, thanks for a great plugin - not having to switch between Octave GUI and VSCode is quite handy.
After some tinkering I've landed with the following launch configuration, which allows me to simply press F5 to launch the currently open file, even if it's using functions from other files in the same directory - similarly to how it works in the Octave GUI.
Additionally I've managed[1] to get the QT plots to mostly[2] work under Windows.
Would you consider updating the default values for
program
andworkingDirectory
of the automatically-populated launch configuration?Additionally I think including this
octave
path example in the Readme would help other Windows users (the escaped inner quotes are crucial!).I've seen the #51 but as it passes the whole filename along with the path to the
program
, I think it won't work if the program uses functions from neighboring files.[1] After spending way too much time debugging and tinkering with environment variables - apparently simply calling
octave-gui
instead ofoctave-cli
allows using QT without setting anything else (no env variables, no paths etc).[2] With
autoTerminate: true
the plot windows close as soon as the program ends, withfalse
they stay on but closing them doesn't work (only stopping the debug); also their contents is not updating (e.g. resising the window doesn't resize the graph) - I believe this is #24?The text was updated successfully, but these errors were encountered: