autoselect device
Quote from bjacquot on February 8, 2024, 5:41 pmIt's been six months since I last used Simulide, and so many changes! Congratulations!
We found it very practical with our students to be able to choose compiler and device in the file.
I've noticed that the BaseDebugger::getInfoInFile( QString line ) method no longer exists. Is it possible to put it back?
https://simulide.forumotion.com/t1331-autoselect-avrgcc
Best regards
It's been six months since I last used Simulide, and so many changes! Congratulations!
We found it very practical with our students to be able to choose compiler and device in the file.
I've noticed that the BaseDebugger::getInfoInFile( QString line ) method no longer exists. Is it possible to put it back?
https://simulide.forumotion.com/t1331-autoselect-avrgcc
Best regards
Quote from arcachofo on February 8, 2024, 6:54 pmHi.
I've noticed that the BaseDebugger::getInfoInFile( QString line ) method no longer exists. Is it possible to put it back?
That functionality is now deprecated, but still supported at CodeEditor::loadConfig().
I didn't realize that device and family was missing (solved at Rev 2192).Now Compiler configurations, breakpoints and files opened (and any future setting) can be saved to a configuration file.
You can activate it in File Settings->Save Setting at file close.
And choose which actions to perform when file is opened again.
Hi.
I've noticed that the BaseDebugger::getInfoInFile( QString line ) method no longer exists. Is it possible to put it back?
That functionality is now deprecated, but still supported at CodeEditor::loadConfig().
I didn't realize that device and family was missing (solved at Rev 2192).
Now Compiler configurations, breakpoints and files opened (and any future setting) can be saved to a configuration file.
You can activate it in File Settings->Save Setting at file close.
And choose which actions to perform when file is opened again.
Quote from bjacquot on February 8, 2024, 7:58 pmThanks.
Now Compiler configurations, breakpoints and files opened (and any future setting) can be saved to a configuration file.
Yes I saw that, and it's a very interesting feature.
The problem is that our students won't have the files in the same directory ( maybe /home/user/simulide/ ).
I modified the .cfg file to have a relative path ( Circuit="./td2-scrutation.sim1" ) but it doesn't work.
I haven't gone deeper to find a solution yet.
Thanks.
Now Compiler configurations, breakpoints and files opened (and any future setting) can be saved to a configuration file.
Yes I saw that, and it's a very interesting feature.
The problem is that our students won't have the files in the same directory ( maybe /home/user/simulide/ ).
I modified the .cfg file to have a relative path ( Circuit="./td2-scrutation.sim1" ) but it doesn't work.
I haven't gone deeper to find a solution yet.
Quote from arcachofo on February 8, 2024, 8:11 pmThe problem is that our students won't have the files in the same directory ( maybe /home/user/simulide/
I see...
I will have a look and try to use relative paths.
The problem is that our students won't have the files in the same directory ( maybe /home/user/simulide/
I see...
I will have a look and try to use relative paths.