On that note about adding the ability to issue "WARNING" and "ERROR" messages
that are highlited, how about also a "NOTICE" message that is also highlited
but for things that aren't necessarily a problem.
Alternatively, I'd probably prefer "color=" and "bgcolor=" parameters added
to echo, so we can just specify colors for our messages and lead off with
whatever capitalized text we want to (after the "ECHO:" bit, of course) if
we want any at all.
Just use the same color options as already available for the "color"
command.
Too bad this:
*color("red") echo("This should be red text.");*
doesn't work. :)
thehans wrote
> The current formatting code is in mainwin.cc:consoleOutput function (
>
https://github.com/openscad/openscad/blob/2a943a57f9d23511c0021b228dee6b6eb9ae440d/src/mainwin.cc#L2923-L2946> ) , and it works by checking if the message starts with "WARNING:", or
> "ERROR:" etc to highlight those messages in different colors. In the most
> recent builds, since Dec. 11, the echo appends plain text only to the
> console, and those specific formatting options can't be invoked directly
> by
> the user(they couldn't before either) because echo() statements always
> start with "ECHO:"
>
> So another option which could be useful is if scripts were able to apply
> some of those builtin formats to highlight their own warnings (and maybe
> errors?) without requiring html either. So for example echo() could take
> an optional "message_type" parameter that would alter its prefix from
> "ECHO:" to some other from a list of pre-defined options. If we did
> something like that we might also want to differentiate between messages
> coming from the application, vs those coming from a script. Maybe prefix
> "SCRIPT-WARNING:" instead of "WARNING:" etc.
--
Sent from:
http://forum.openscad.org/_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Locked
