Auto reload and preview behaviour?
I haven't used this much lately.
Having turned it on for testing I noticed what I think is strange behaviour.
File/New, paste some code [in this case issue #3527 - crashing code],
File/Save-as, type name, Enter, CRASH!
Save-as was followed by auto reload and preview.
2019.05 same.
2015.03 does not reload/preview.
I don't think it should reload on Save-as.
Bug or Feature?
OpenSCAD Admin - email* me if you need anything, or if I've done something stupid...
- on the Forum, click on my MichaelAtOz label, there is a link to email me.
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
--
Sent from: http://forum.openscad.org/
If nobody screams I'll report this as a bug.
-----Original Message-----
From: Discuss [mailto:discuss-bounces@lists.openscad.org] On Behalf Of MichaelAtOz
Sent: Fri, 11 Dec 2020 13:21
To: discuss@lists.openscad.org
Subject: [OpenSCAD] Auto reload and preview behaviour?
I haven't used this much lately.
Having turned it on for testing I noticed what I think is strange behaviour.
File/New, paste some code [in this case issue #3527 - crashing code],
File/Save-as, type name, Enter, CRASH!
Save-as was followed by auto reload and preview.
2019.05 same.
2015.03 does not reload/preview.
I don't think it should reload on Save-as.
Bug or Feature?
OpenSCAD Admin - email* me if you need anything, or if I've done something stupid...
- on the Forum, click on my MichaelAtOz label, there is a link to email me.
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the
extent possible under law, I have waived all copyright and related or neighbouring rights
to this work. Obviously inclusion of works of previous authors is not included in the
above.
--
Sent from: http://forum.openscad.org/
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
--
This email has been checked for viruses by AVG.
https://www.avg.com
I agree.
Also, it would be nice if it detected a previous crash, and offered to open
the backup file, without trying to rendering it, on the next start.
Now, I'll have to open it in another editor, fix the error, open an empty
project, paste the edited version and save as over the original. Not that
hard, but a chain of steps that can be effed up badly if you don't pay
attention.
--
Sent from: http://forum.openscad.org/
Can the whole rendering process not be run in a try/catch block and have a
message box show a suitable error message if an exception is thrown. That
way if rendering fails it does not blow out the app.
On Sun, Dec 13, 2020, 16:22 Troberg troberg.anders@gmail.com wrote:
I agree.
Also, it would be nice if it detected a previous crash, and offered to open
the backup file, without trying to rendering it, on the next start.
Now, I'll have to open it in another editor, fix the error, open an empty
project, paste the edited version and save as over the original. Not that
hard, but a chain of steps that can be effed up badly if you don't pay
attention.
--
Sent from: http://forum.openscad.org/
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
It already does if i remember correctly. Try/catch just doesn't help for a
null pointer dereference.
Anyways I feel like crashes are fairly rare(particularly once a stable
release is finalized), and usually very promptly fixed once identified.
The crash above was fixed within a day.
So I'm not sure it's worth the effort to add special handling of crashes as
a new feature.
On Sun, Dec 13, 2020 at 3:06 AM Tim Hawkins tim.thawkins@gmail.com wrote:
Can the whole rendering process not be run in a try/catch block and have a
message box show a suitable error message if an exception is thrown. That
way if rendering fails it does not blow out the app.
On Sun, Dec 13, 2020, 16:22 Troberg troberg.anders@gmail.com wrote:
I agree.
Also, it would be nice if it detected a previous crash, and offered to
open
the backup file, without trying to rendering it, on the next start.
Now, I'll have to open it in another editor, fix the error, open an empty
project, paste the edited version and save as over the original. Not that
hard, but a chain of steps that can be effed up badly if you don't pay
attention.
--
Sent from: http://forum.openscad.org/
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
thehans wrote
Anyways I feel like crashes are fairly rare(particularly once a stable
release is finalized), and usually very promptly fixed once identified.
The crash above was fixed within a day.
So I'm not sure it's worth the effort to add special handling of crashes
as
a new feature.
I don't get crashes that often, but it's not uncommon to do something stupid
so that it locks up in a "forever-render" which can't be cancelled, so I
have to kill the process.
This brings another issue to mind: A cancel button that's actually
responsive all the time, and which can always cancel a render.
--
Sent from: http://forum.openscad.org/
Troberg wrote
it's not uncommon to do something stupid
so that it locks up in a "forever-render" which can't be cancelled, so I
have to kill the process.
This brings another issue to mind: A cancel button that's actually
responsive all the time, and which can always cancel a render.
There is an issue on GitHub, asking to do Preview/F5 in a separate thread,
so it can be cancelled, like Render/F6.
ATM there is a 'X' button at the progress bar for Render/F6, but it is CGAL
granular, so if it is the final big union, it has to finish before
cancelling.
OpenSCAD Admin - email* me if you need anything, or if I've done something stupid...
- on the Forum, click on my MichaelAtOz label, there is a link to email me.
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
--
Sent from: http://forum.openscad.org/
Troberg may have been focusing on complex objects that are so difficult
to view on the screen (after F5) that OpenSCAD becomes unresponsive to
any input and has to be killed. I am doing increasingly complex
projects, and this happens to me frequently. This is one reason I have
moved some projects to AngelCAD: the rendering time is much shorter and
I can then actually view the object, rather than having to kill it.
Sorry that I do not have a constructive suggestion for how to improve
OpenSCAD in this particular regard
Jon
On 12/13/2020 6:58 AM, MichaelAtOz wrote:
Troberg wrote
it's not uncommon to do something stupid
so that it locks up in a "forever-render" which can't be cancelled, so I
have to kill the process.
This brings another issue to mind: A cancel button that's actually
responsive all the time, and which can always cancel a render.
There is an issue on GitHub, asking to do Preview/F5 in a separate thread,
so it can be cancelled, like Render/F6.
ATM there is a 'X' button at the progress bar for Render/F6, but it is CGAL
granular, so if it is the final big union, it has to finish before
cancelling.
There is a simple example where F5 becomes unresponsive here:
https://github.com/openscad/openscad/issues/3535
It seems that a nested difference explodes in OpenCSG complexity. The
simple solution is to add a render because GCAL doesn't find it too
difficult and of course doing it in 2D is much faster.
On Sun, 13 Dec 2020 at 12:40, jon jon@jonbondy.com wrote:
Troberg may have been focusing on complex objects that are so difficult
to view on the screen (after F5) that OpenSCAD becomes unresponsive to
any input and has to be killed. I am doing increasingly complex
projects, and this happens to me frequently. This is one reason I have
moved some projects to AngelCAD: the rendering time is much shorter and
I can then actually view the object, rather than having to kill it.
Sorry that I do not have a constructive suggestion for how to improve
OpenSCAD in this particular regard
Jon
On 12/13/2020 6:58 AM, MichaelAtOz wrote:
Troberg wrote
it's not uncommon to do something stupid
so that it locks up in a "forever-render" which can't be cancelled, so I
have to kill the process.
This brings another issue to mind: A cancel button that's actually
responsive all the time, and which can always cancel a render.
There is an issue on GitHub, asking to do Preview/F5 in a separate
thread,
so it can be cancelled, like Render/F6.
ATM there is a 'X' button at the progress bar for Render/F6, but it is
CGAL
granular, so if it is the final big union, it has to finish before
cancelling.
nophead wrote
It seems that a nested difference explodes in OpenCSG complexity. The
simple solution is to add a render because GCAL doesn't find it too
difficult and of course doing it in 2D is much faster.
Yep, that is usually my problem. I add a seemingly harmless difference, and
it locks up. Adding a render solves it.
--
Sent from: http://forum.openscad.org/