|
 |
The options:
All of the following:
+-ga all_console all_file
+-gd debug_console debug_file
+-gf fatal_console fatal_file
+-gr render_console render_file
+-gs statistic_console statistic_file
+-gw warning_console warning_file
+-gp append_file
and
+-wl warning_level
have been replaced with a message set of streams and a trouble set of
streams further grouped by a 'modular grouping':
+m_af_ -m_af_ message_animation_filename
+m_al -m_al message_animation_level
+t_af_ -t_af_ trouble_animation_filename
+t_al -t_al trouble_animation_level
+m_bf_ -m_bf_ message_bound_filename
+m_bl -m_bl message_bound_level
+t_bf_ -t_bf_ trouble_bound_filename
+t_bl -t_bl trouble_bound_level
+m_if_ -m_if_ message_image_filename
+m_il -m_il message_image_level
+t_if_ -t_if_ trouble_image_filename
+t_il -t_il trouble_image_level
+m_mf_ -m_mf_ message_master_filename
+m_ml -m_ml message_master_level
+t_mf_ -t_mf_ trouble_master_filename
+t_ml -t_ml trouble_master_level
+m_of_ -m_of_ message_options_filename
+m_ol -m_ol message_options_level
+t_of_ -t_of_ trouble_options_filename
+t_ol -t_ol trouble_options_level
+m_pf_ -m_pf_ message_parse_filename
+m_pl -m_pl message_parse_level
+t_pf_ -t_pf_ trouble_parse_filename
+t_pl -t_pl trouble_parse_level
+m_phof_ -m_phof_ message_photons_filename
+m_phol -m_phol message_photons_level
+t_phof_ -t_phof_ trouble_photons_filename
+t_phol -t_phol trouble_photons_level
+m_radf_ -m_radf_ message_radiosity_filename
+m_radl -m_radl message_radiosity_level
+t_radf_ -t_radf_ trouble_radiosity_filename
+t_radl -t_radl trouble_radiosity_level
+m_rf_ -m_rf_ message_render_filename
+m_rl -m_rl message_render_level
+t_rf_ -t_rf_ trouble_render_filename
+t_rl -t_rl trouble_render_level
+m_uf_ -m_uf_ message_user_filename
+m_ul -m_ul message_user_level
+t_uf_ -t_uf_ trouble_user_filename
+t_ul -t_ul trouble_user_level
The _level is a 0-8 value with 8 reporting everything and 0 nothing -
except for the trouble streams where errors are always reported. Like
the current code all stream output goes to stderr by default unless
directed to a file.
Unlike, official POV-Ray output cannot be set up to be written to both
stderr and to files. Lastly (lying), there is no all output file option.
Lastly, the odd default naming when only using on|off strings over file
names is being deleted.
The options parsing for these replacements streams is mostly there, but
that's it. I have not wired them up so to speak. Additional groupings or
sub-groups might make sense too over time.
I have some dreams about versioning / version looping outputs by
directories in general - for which there is currently no code at all,
but with which these stream outputs would be tangled.
Bill P.
Post a reply to this message
|
|
|
|
hi,
William F Pokorny <ano### [at] anonymous org> wrote:
> The options:
> All of the following:
> ...
> have been replaced with a message set of streams and a trouble set of
> streams further grouped by a 'modular grouping':
> ...
>
> The _level is ... except ...
</sigh>
> ...
> I have some dreams ...
nightmares, I should not wonder.. will there be a "POV-Ray Yuqk option
translate" ("Peyote" :-)) utility ?
regards, jr.
Post a reply to this message
|
|
|
|
On 6/6/25 12:54, jr wrote:
> nightmares, I should not wonder.. will there be a "POV-Ray Yuqk option
> translate" ("Peyote" :-)) utility ?
:-) Yep. Pretty much every day working on this I feel like quitting
again. But, I cannot shake that an options re-work needs to happen for
v4 and the game I want to personally play, so I'm trying hard to push
through to something 'new-working' this time around.
As for auto-translators I have thought about them, but more in the
context of all the SDL changes I've made than with these options changes.
Those using the shipped vim highlighting will have an idea about most of
what is now in error new or so on in SDL, but of course not everyone
uses vim. Plus, I couldn't figure out how to get the (non-language
based) syntax checking to flag certain things reliably.
My POV-Ray option sets are relatively small 10 or less - a page or two
at most - so I think updates should mostly be quick with the new code
telling me what to do. Do other have really huge option sets for some
reason I missed?
The moves of the photon and radiosity block settings from the parser to
options parsing will be more work, but also pretty much one for one by
name(*). With these settings in options I guess the option sets will be
larger as used, though, I hope in the end people will just be able to
mostly reference different, say, radiosity quality levels by pre-shipped
file settings.
Aside: One thing I should have mentioned is all of the different _level
settings could be combined into two (one each for message/trouble).
There are a bunch of them currently because it helps me while developing
to be able to look at things by sets / types.
Bill P.
(*) - Expect some around long enough to know some the radiosity settings
will be moving back into the options stage where they were initially.
Post a reply to this message
|
|
