Re: Custom Dialog Problems and Observations

Thank you for your prompt attention to the matter.
I'm glad that I have helped out in some small way.

I have uploaded the revised master and checked it out. It does indeed fix
the issue I had in this case. And now, I realize that my comment about
choosing property names wisely was sheer rubbish. I have no choice in the
matter as they are all predetermined. But rather than having to revise the
list of properties and values manually, I was suggesting/hoping for some
way to move up/down the list with selectors or some other means.

With regards to the sequence I have been using
Frame->sizer->panel->sizer.... except in this case of the speedmeter where
I started with what was provided. I notice that wxGlade-0,9,9pre enforces
the paradigm you suggested. No argument from me. I also noted that the code
generated by 0.9.9pre does not include class functions __set_properties and
__set_layout. Everything is rolled up into the __init__ function. I am not
a fan of this style and I hope this is not a permanent change or have I
missed a toggle in the wxglade application to alter this behaviour. I like
the organization these class functions provide.

I read in one of your replies on the issue trackers that you were planning
to provide, in v1.1, complete listing of event types in the event panel.
Are you considering the same for all available properties for widgets? I'm
sure you have.

Thanks for the time.

Regards

--
------------------------------
*Lawrence Gray*


------------------------------




On Fri, 24 Apr 2020 at 14:17, Dietmar Schwertberger <
[email protected]> wrote:

> On 24.04.2020 07:50, Lawrence Gray wrote:
> > Initially, I thought that the code would be generated in the order the
> > properties were listed in the code pane and I am wondering if there is
> > any way to rearrange the list of properties and force the code
> > generator to respect the listed order.  This might be a useful
> > enhancement but I will let others decide as I don't know if this is
> > overall a significant problem.
>
> This is indeed a bit unexpected. I would not have known this...
>
> I have just fixed this in the master branch.
>
> Actually, I rarely use the properties myself and they are just there
> because they have always been. As workaround you could have added the
> property code to "Code to be inserted after".
>
> If you ever want to run your program on Windows, you should add a panel:
> Frame -> Panel -> Sizer
> Without, the frame looks too dark and you can't easily use Tab and
> Shift+Tab to navigate.
>
> Regards,
>
> Dietmar
>
>
>
> _______________________________________________
> wxGlade-general mailing list
> wxGlade-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/wxglade-general
>

_______________________________________________
wxGlade-general mailing list
wxGlade-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/wxglade-general