Introduce a limit for warnings in a compile
As far as I know, there is currenty no means to break execution during a F5
and F6 compile. This gets especially a nasty problem, when OpenSCAD decides
to emit a very large number of warnings, e.g. when compiling some older
code. Sometimes also a simple initalization bug can cause such a behaviour.
Then it can happen that you have to wait minutes (up to and years) until
control comes back.
Wouldn't make it sense to introduce a limit on the number of warnings a
compile can output?
--
Sent from: http://forum.openscad.org/
I think the bigger issue is that you can't pause or stop execution. With a
complex model, you really want to be able to break a 3 minute render you
started, and then noticed an error in the code...
--
Sent from: http://forum.openscad.org/
Yeah!
During F6 you can save your work, quit OpenSCAD and restart. But during F5
you rely on killing the task and can only continue with the lastest backup,
if you didn't explicitly save your work.
So in practice you make a typo in a variable name and get a million warnings
on a sweep, without any chance to break, or being able to find the reason
because of myriads warnings after control is back.
--
Sent from: http://forum.openscad.org/
Have you tried turning on "Stop on first warning" in preferences?
On Mon, 25 Mar 2019 at 10:36, Parkinbot rudolf@digitaldocument.de wrote:
Yeah!
During F6 you can save your work, quit OpenSCAD and restart. But during F5
you rely on killing the task and can only continue with the lastest backup,
if you didn't explicitly save your work.
So in practice you make a typo in a variable name and get a million
warnings
on a sweep, without any chance to break, or being able to find the reason
because of myriads warnings after control is back.
--
Sent from: http://forum.openscad.org/
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
On Mon, Mar 25, 2019 at 10:41:56AM +0000, nop head wrote:
Have you tried turning on "Stop on first warning" in preferences?
I would count that as a "workaround", and not as a solution.
In practice, users will encounter this problem when they least expect
it and (almost) never when they have prepared for it. So being able to
abort a lenghty render remains something that should be possible.
Imagine if I have a big project and:
// this was guessed/aproximated from the preview...
// translate ([30,40,50]) cube ([24, 28,33]);
// ... now with the proper calculations:
translate ([sin (angle1)*len3, cos(angle1)*len3, len4])
cube ([atan(angle2)*len5, .... ]);
where you've worked an hour to determine the sin/cos atan etc stuff
but then end up in the un-interruptible stream of warnings due to a
typo. Losing the work on those coordinates would cause a lot of
frustration....
Roger.
On Mon, 25 Mar 2019 at 10:36, Parkinbot rudolf@digitaldocument.de wrote:
Yeah!
During F6 you can save your work, quit OpenSCAD and restart. But during F5
you rely on killing the task and can only continue with the lastest backup,
if you didn't explicitly save your work.
So in practice you make a typo in a variable name and get a million
warnings
on a sweep, without any chance to break, or being able to find the reason
because of myriads warnings after control is back.
--
Sent from: http://forum.openscad.org/
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.
Yes but with stop on first warning you get one warning and it stops. You
fix that and F5 again and so on. It only goes on to the uninterruptible
preview if it is clear of warnings. Yes it would be nice to interrupt that
and sometime I can because sometimes it gives the progress bar with the
cancel option and sometimes not, I think.
On Mon, 25 Mar 2019 at 11:00, Rogier Wolff R.E.Wolff@bitwizard.nl wrote:
On Mon, Mar 25, 2019 at 10:41:56AM +0000, nop head wrote:
Have you tried turning on "Stop on first warning" in preferences?
I would count that as a "workaround", and not as a solution.
In practice, users will encounter this problem when they least expect
it and (almost) never when they have prepared for it. So being able to
abort a lenghty render remains something that should be possible.
Imagine if I have a big project and:
// this was guessed/aproximated from the preview...
// translate ([30,40,50]) cube ([24, 28,33]);
// ... now with the proper calculations:
translate ([sin (angle1)*len3, cos(angle1)*len3, len4])
cube ([atan(angle2)*len5, .... ]);
where you've worked an hour to determine the sin/cos atan etc stuff
but then end up in the un-interruptible stream of warnings due to a
typo. Losing the work on those coordinates would cause a lot of
frustration....
Roger.
On Mon, 25 Mar 2019 at 10:36, Parkinbot rudolf@digitaldocument.de
wrote:
Yeah!
During F6 you can save your work, quit OpenSCAD and restart. But
during F5
you rely on killing the task and can only continue with the lastest
backup,
if you didn't explicitly save your work.
So in practice you make a typo in a variable name and get a million
warnings
on a sweep, without any chance to break, or being able to find the
reason
because of myriads warnings after control is back.
--
Sent from: http://forum.openscad.org/
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110
**
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
nophead wrote
Yes but with stop on first warning you get one warning and it stops. You
fix that and F5 again and so on. It only goes on to the uninterruptible
Thanks, I didn't know this. I would be better if the option was "stop after
20 warnings" or so, but it lets you work at least.
--
Sent from: http://forum.openscad.org/
nophead wrote
Have you tried turning on "Stop on first warning" in preferences?
That'll work for syntax errors, but not when you press F5, just to realize
that you forgot to change a value, or see that you accidentally misplaced a
decimal point. Then, you'll have to wait for a few minutes for something you
know will be wrong.
To be able to abort would be great, and something I'd use a lot.
--
Sent from: http://forum.openscad.org/
Not just syntax errors but also warnings about bad values, etc, but not
typos that don't generate any warnings. But don't you need to see the
render to spot those anyway?
On Tue, 26 Mar 2019 at 06:41, Troberg troberg.anders@gmail.com wrote:
nophead wrote
Have you tried turning on "Stop on first warning" in preferences?
That'll work for syntax errors, but not when you press F5, just to realize
that you forgot to change a value, or see that you accidentally misplaced a
decimal point. Then, you'll have to wait for a few minutes for something
you
know will be wrong.
To be able to abort would be great, and something I'd use a lot.
--
Sent from: http://forum.openscad.org/
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
nophead wrote
Not just syntax errors but also warnings about bad values, etc, but not
typos that don't generate any warnings. But don't you need to see the
render to spot those anyway?
Sometimes, but many times I see a screwup the second I hit F5. For example,
intending to change 12 to -12 on a bunch of lines, but inadvertedly changing
it to 1-2 on one of them.
--
Sent from: http://forum.openscad.org/