Viktor, I've got all these cases of the missing VR/VR3 taken care of but 
before I push the changes up where you can try them, I'd appreciate your 
thoughts on a few things.

First, I have followed the way that the current system creates layouts that 
include VR or VR3.  They set up a place for it but don't actually put 
VR/VR3 into it and show the widget unless it's already open and shown. It 
seems to me that if one asks for a layout that includes VR/VR3 that they 
would expect VR/VR3 will immediately be visible in that layout.  What do 
you think?

Second, I have some layouts that use VR and some that use VR3.  I think 
that these layouts should (like, for example, "Big Tree") should open with 
VR3 if available otherwise with VR.  That will be a little tricky to 
arrange but I think it can be done.  Do you have an opinion here?

The third thing I would welcome your opinion on is about which layouts 
should be included in the core code vs which ones could be defined in 
@settings tree.  The Layout-Demo outline uses a mix of both. My thinking is 
that some layouts may only be useful to a few users (like me or you!) 
whereas others would see more widespread use. Of course new layouts can be 
created by anyone - if they can do the small amount of scripting - and put 
into an @settings tree. I'm unsure where to draw the line between core 
commands and non-core ones.  What is your opinion?

Implementing any of these thoughts will take me some little time and need 
some testing as well.

Thanks!

On Monday, October 7, 2024 at 4:13:27 AM UTC-4 viktor....@gmail.com wrote:

> Hello Thomas,
>
> tbp1...@gmail.com schrieb am Sonntag, 6. Oktober 2024 um 23:23:19 UTC+2:
>
> On Sunday, October 6, 2024 at 5:17:22 PM UTC-4 viktor....@gmail.com wrote:
>
> Hello Thomas,
>
> tbp1...@gmail.com schrieb am Sonntag, 6. Oktober 2024 um 22:51:45 UTC+2:
>
> Than you for testing.  It looks like you do not have the viewendered.py 
> plugin enabled.
>
>
> Correct - but - as you can see in "Log-002" viewrendered3.py is enabled ! 
> - I never enable VR & VR3 at the same time ...
>
>
> I do usually enable them both at the same time.  I don't recall if I have 
> ever tested any code with only one enabled. It looks like I will have to 
> start doing that.
>
>
> *First the good news: After I enabled 'viewrendered.py' plugin in addition 
> this morning, the tracebacks are gone ! *
>
> Since I did all my tests of your initial script-based layout demo ONLY 
> with 'viewrendered3.py' successfully, I assumed that enabling only VR3 
> SHOULD be sufficient ...
>
> I'll continue my tests & will report any issues I'll encounter.
>
> With kind regards,
>
> Viktor
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/894d4499-4861-406d-8972-a9f1e9268811n%40googlegroups.com.

Reply via email to