My startup script changes graphics_toolkit from gnuplot to qt, and I see it's not applied until I manually run the script
That do you mean by 'startup script'? Is it .octaverc startup script? I have been tested this, and .octaverc run in Cantor Octave backend and also graphics_toolkit works too.
I confirm that .octaverc is executed at startup (the paths that I added there are visible in Cantor). However: - Cantor executes some code afterwards and overrides its content, for instance: I set as specific graphics_toolkit qt, yet once I check it in cantor it says gnuplot and I need to specify it again manually in each session. - Octave's workspace at startup is not initially seen in Cantor workspace. For instance, I set a variable in .octaverc like this `x = 2;` and it does not appear in Cantor workspace, but if I then type in the console `x`, Cantor correctly returns `2` at the time `x` and its value is added to the workspace. So, can we make .octaverc the last bit that is executed at startup and have Cantor display Octave's initial workspace? Also, I cannot confirm that the script I configure in cantor octave backend settings is executed. Following the example above, I set a file in there where I have `x = 2;` and when I test it in Cantor, it says x is undefined, unlike when I do the same in .octaverc.
Created attachment 128165 [details] Autorun script for changing graphics_toolkit
(In reply to avlas from comment #2) > I confirm that .octaverc is executed at startup (the paths that I added > there are visible in Cantor). However: > > - Cantor executes some code afterwards and overrides its content, for > instance: I set as specific graphics_toolkit qt, yet once I check it in > cantor it says gnuplot and I need to specify it again manually in each > session. Yes, I have been checked code, and Cantor really set gnuplot as graphics toolkit, when integrated graphics enabled. But you actually haven't need to change it to 'qt' manually - use autorun scripts from Octave settings. I have been add example (attachment #1 [details]). > - Octave's workspace at startup is not initially seen in Cantor workspace. > For instance, I set a variable in .octaverc like this `x = 2;` and it does > not appear in Cantor workspace, but if I then type in the console `x`, > Cantor correctly returns `2` at the time `x` and its value is added to the > workspace. Is you write 'x' in first executed entry? Because Cantor update variable list (variable manager) only first executed entry. For example, my .octaverc works as expected, see attachment #2 [details] > So, can we make .octaverc the last bit that is executed at startup and have > Cantor display Octave's initial workspace? .octaverc can't be executed before Cantor startup because, Cantor init used --eval octave option. But I think, Cantor can improve currect behaviour, because the idea of changing graphics toolkit to gnuplot is avoiding default fltk, which can freeze octave program (and Cantor too) at all. So, instead of current "always change toolkit" we can use "change toolkit if fltk" and I think, this will be solve your problem, because you use 'qt' toolkit, not 'fltk' toolkit. > Also, I cannot confirm that the script I configure in cantor octave backend > settings is executed. Following the example above, I set a file in there > where I have `x = 2;` and when I test it in Cantor, it says x is undefined, > unlike when I do the same in .octaverc. Well, this is strange. Do you sure, that after writing "x = 2;" you have pressed "Add" button? Because this is needed for actual adding script to autorun, see my attachment #3 [details]
Created attachment 128166 [details] Cantor and .octaverc
Created attachment 128167 [details] Example of using autorun scripts
> the idea of changing graphics toolkit to gnuplot is avoiding default fltk, which can freeze octave program (and Cantor too) at all. So, instead of current "always change toolkit" we can use "change toolkit if fltk" and I think, this will be solve your problem, because you use 'qt' toolkit, not 'fltk' toolkit FYI, qt graphics is default in octave for quite some releases now, so this solution you propose I think it's the way to go for the case a user overrides the default with fltk in .octaverc
I see, I totally misundderstood the autorun scripts, I thought there were script files to run, not just octave commands, so I tried with the file path to an m file, and nothing happened, now I understand. Thanks! Could you please also take a look at https://bugs.kde.org/show_bug.cgi?id=420959? (plots fail in my end no matter the graphics toolkit)
(In reply to avlas from comment #7) > FYI, qt graphics is default in octave for quite some releases now, so this > solution you propose I think it's the way to go for the case a user > overrides the default with fltk in .octaverc And I would suggest replacing ftlk with qt instead of gnuplot because, as I said, qt is default in Octave
(In reply to avlas from comment #9) > (In reply to avlas from comment #7) > > > FYI, qt graphics is default in octave for quite some releases now, so this > > solution you propose I think it's the way to go for the case a user > > overrides the default with fltk in .octaverc > > And I would suggest replacing ftlk with qt instead of gnuplot because, as I > said, qt is default in Octave I think, this depends from disto, for example on my system octave 4.2.2 'qt' toolkit just not available (not mentioned in `available_graphics_toolkits`) and fltk is a default (and this toolkit is broken, of course). Of course, octave 4 is outdated now, but I think, better support situation like this, because it is not very difficult for Cantor to do it.
(In reply to Nikita Sirgienko from comment #10) > (In reply to avlas from comment #9) > > (In reply to avlas from comment #7) > > > > > FYI, qt graphics is default in octave for quite some releases now, so this > > > solution you propose I think it's the way to go for the case a user > > > overrides the default with fltk in .octaverc > > > > And I would suggest replacing ftlk with qt instead of gnuplot because, as I > > said, qt is default in Octave > > I think, this depends from disto, for example on my system octave 4.2.2 'qt' > toolkit just not available (not mentioned in `available_graphics_toolkits`) > and fltk is a default (and this toolkit is broken, of course). > Of course, octave 4 is outdated now, but I think, better support situation > like this, because it is not very difficult for Cantor to do it. Sounds good
(In reply to avlas from comment #8) > I see, I totally misundderstood the autorun scripts, I thought there were > script files to run, not just octave commands, so I tried with the file path > to an m file, and nothing happened, now I understand. This is just to confirm that if I replace in autorun scripts the path to cantor_startup.m in ~/.local/share/cantor/octavebackend/ (folder that cantor adds to the octave path at startup), to just the command `cantor_startup`, it just works. It's quite obvious but just wanted to mention for the case someone would like to create an external cantor_startup script instead of pasting one by one in cantor settings.
(In reply to avlas from comment #12) > (In reply to avlas from comment #8) > > I see, I totally misundderstood the autorun scripts, I thought there were > > script files to run, not just octave commands, so I tried with the file path > > to an m file, and nothing happened, now I understand. > > This is just to confirm that if I replace in autorun scripts the path to > cantor_startup.m in ~/.local/share/cantor/octavebackend/ (folder that cantor > adds to the octave path at startup), to just the command `cantor_startup`, > it just works. It's quite obvious but just wanted to mention for the case > someone would like to create an external cantor_startup script instead of > pasting one by one in cantor settings. I suppose, that Cantor just need rename 'autorun scripts' to 'autorun commands', which is actually more accurate. I think, this will be prevent future misunderstanding.
(In reply to Nikita Sirgienko from comment #13) > (In reply to avlas from comment #12) > > (In reply to avlas from comment #8) > > > I see, I totally misundderstood the autorun scripts, I thought there were > > > script files to run, not just octave commands, so I tried with the file path > > > to an m file, and nothing happened, now I understand. > > > > This is just to confirm that if I replace in autorun scripts the path to > > cantor_startup.m in ~/.local/share/cantor/octavebackend/ (folder that cantor > > adds to the octave path at startup), to just the command `cantor_startup`, > > it just works. It's quite obvious but just wanted to mention for the case > > someone would like to create an external cantor_startup script instead of > > pasting one by one in cantor settings. > > I suppose, that Cantor just need rename 'autorun scripts' to 'autorun > commands', which is actually more accurate. I think, this will be prevent > future misunderstanding. Yeah, that'd be good :)