On 4/19/21 11:26 AM, jr wrote:
> hi,
> 
> William F Pokorny <ano### [at] anonymousorg> wrote:
>> On 4/18/21 6:46 AM, jr wrote:
>>> ...
>> Yes, please post. ...
> > attached.

Thanks.

> 
...
> 
> makes one wonder how people actually use dictionaries.  are more than, say, 15
> or 20 keys common?  (personally, less than 10, always, I'd say)  maybe a
> "survey" on new (to 3.8) features' uptake?
> 

Don't know. I think the dictionary feature is still new enough (and it's 
been buggy enough), we don't know what sizes would be common.

The concern over the behavior of the token hashing function for the 
symbol table(s) applies to much more than dictionaries. This code is 
used during parsing and at run time for variables in the function calls 
for isosurfaces and parametrics. Part of why, for performance, it's best 
to set up functions for isosurfaces and parametrics as fully resolved as 
possible at the final use in those objects.

> a couple of 'povr' questions.  when will you make the lowercase-able version
> available?  would you consider a feature request for a "-windowid" command-line
> option to supply an X window to 'povr'?
> 

As for another povr branch release, I have no firm date in mind at the 
moment. I'm still significantly hung up on documentation(how) and 
strongly related is what to do with all the ini, config, flag, 
global_settings and environment variable inputs at the front of each 
POV-Ray execution.

Aside: Stumbled across another option the other day; long in the code, 
but apparently never documented (Include_ini?).

I'd like to make that big, not completely functional or consistent 
tangle of code simpler and self documenting - with a capability for 
localized translations, but, how... I've got some starts / tests in the 
code, but nothing I'd consider anywhere near complete. Been looking some 
at Rust, which has a popular and powerful command line options package. 
I was thinking maybe it could be used as a completely stand alone front 
end generating some standard option setting input file to POV-Ray 
itself. Still just playing / thinking. Likely, such simplification a 
pipe dream, but nothing wrong with dreaming I guess. :-)

Not sure what you are after with the -windowid? Some time back made X11 
the default preview window handler in the povr branch. Though, sdl2 (or 
sdl1.2) is supported too as a command line option. So, by default, there 
is an X window with an id which you can query/grab when POV-Ray is run 
with the preview window. Is that what you are after - to do window 
captures/dumps or similar?

Bill P.

Post a reply to this message