wxglade-general

[wxGlade] Announcing wxPerl 3.006

[Johan V. <jvr...@sq...>]

Dear all,

wxPerl version 3.006 has been released and is available on GitHub.

Major change in 3.006 is a vast overhaul to eliminate depending on
wxWidgets 2.8 and 3.0 compatibility hacks. The code is much cleaner now,
and builds without problems with 3.2, 3.3.0 and 3.3.1 (at this time latest
wxWidgets release). 

This makes wxWidgets future proof! Future releases of wxWidgets
should no longer impose substantial problems.

All tests should succeed. If you are missing features please issue a
request on the issue tracker.

For best results, remove all installed Alien::wxWidgets packages and
install the latest from GitHub.

Release: https://github.com/sciurius/wxPerl/releases
Issues: https://github.com/sciurius/wxPerl/issues
Alien::wxWidgets: https://github.com/sciurius/perl-Alien-wxWidgets/releases/

Re: [wxGlade] Erroneous code (perl, import from pre-wglade 1.0)

[Dietmar S. <mai...@sc...>]

On 5/29/2025 1:33 PM, Johan Vromans wrote:
> sub __set_properties {}
> sub __do_layout {}

Actually, these methods should not be generated at all any more.
Is this with "Keep user code"? The migration might not work 100% 
automatically. You may need to remove them manually.

Regards,

Dietmar

[wxGlade] Erroneous code (perl, import from pre-wglade 1.0)

[Johan V. <jvr...@sq...>]

After importing an ancient project and generate perl code (single-file),
the output contains:

sub __set_properties {
sub __do_layout {

This should be

sub __set_properties {}
sub __do_layout {}

I couldn't figure out where this is caused, so no PR for now...

-- Johan

Re: [wxGlade] Bug report

[Dietmar S. <mai...@sc...>]

On 4/26/2025 3:47 PM, Igor Korot wrote:
> Yes I’m running latest release .

But the traceback was from 1.1.0?

Regarding your screen size: move the splitter upwards and enable "auto 
hide" of the taskbar and you have enough space on screen.

Regards,

Dietmar

Re: [wxGlade] Bug report

[Igor K. <iko...@gm...>]

Hi Dietmar,

Yes I’m running latest release .

Thank you.


On Sat, Apr 26, 2025 at 6:20 AM Dietmar Schwertberger <
mai...@sc...> wrote:

> I could not reproduce the problem. Does it occur on recent versions?
> (1.1.1 or the repository version)
>
> Regards,
>
> Dietmar
>
>
>
> _______________________________________________
> wxGlade-general mailing list
> wxG...@li...
> https://lists.sourceforge.net/lists/listinfo/wxglade-general
>

Re: [wxGlade] Bug report

[Dietmar S. <mai...@sc...>]

I could not reproduce the problem. Does it occur on recent versions?
(1.1.1 or the repository version)

Regards,

Dietmar

Re: [wxGlade] Issue with wxGlade

[Dietmar S. <mai...@sc...>]

The behaviour of the sizer where the grid/list is placed is not optimal.
But would you really like to use a screen layout where the actual 
property editor window is only a few pixels high even though the Palette 
above has empty space?
Increase the height of the Properties panel and you can edit:

A vertical screen resolution of 768 pixels has been common more than 
twenty years ago. I don't think it makes sense to invest time into 
supporting this for a developer tool nowadays. Even on my crappy company 
notebook I have 1920×1080 and I'm using wxGlade on this a lot. (Most 
developer tools require a larger screen for development than for usage, 
but wxGlade does not.)

Regards,

Dietmar

Re: [wxGlade] Issue with wxGlade

[Igor K. <iko...@gm...>]

Hi, Dietmar,

Attached.

Thank you,


On Thu, Apr 24, 2025 at 12:01 PM Dietmar Schwertberger
<mai...@sc...> wrote:
>
> On 4/24/2025 6:23 PM, Igor Korot wrote:
> > In order to edit it need to see a control. And after clicking the
> > "Add" button it's not visible.
> >
> You're not seeing the grid / list ?
>
> Please post a screenshot.
>
> Regards,
>
> Dietmar
>
>
>
> _______________________________________________
> wxGlade-general mailing list
> wxG...@li...
> https://lists.sourceforge.net/lists/listinfo/wxglade-general

Re: [wxGlade] Issue with wxGlade

[Dietmar S. <mai...@sc...>]

On 4/24/2025 6:23 PM, Igor Korot wrote:
> In order to edit it need to see a control. And after clicking the 
> "Add" button it's not visible.
>
You're not seeing the grid / list ?

Please post a screenshot.

Regards,

Dietmar

Re: [wxGlade] Issue with wxGlade

[Igor K. <iko...@gm...>]

Hi, Dietmar,

On Thu, Apr 24, 2025, 9:54 AM Dietmar Schwertberger <
mai...@sc...> wrote:

> On 4/23/2025 7:01 AM, Igor Korot wrote:
>
>  You will notice that the text control t enter the text
> for the choices is not visible.
>
> A text control will only be shown if you set Preferences -> Accessibility
> -> "Show editors for Grid Properties".
> This is due to bad support of the wxGrid implementation for screen readers.
> (I did a  PR for wxWidgets to change this, but it has not yet propagated
> into wxPython.)
>
> Normally, that's not required. You can just edit inside the grid:
>

In order to edit it need to see a control. And after clicking the "Add"
button it's not visible.

I set an option for now.

Thank you.


>
> Regards,
>
> Dietmar
> _______________________________________________
> wxGlade-general mailing list
> wxG...@li...
> https://lists.sourceforge.net/lists/listinfo/wxglade-general
>

Re: [wxGlade] Issue with wxGlade

[Dietmar S. <mai...@sc...>]

On 4/23/2025 7:01 AM, Igor Korot wrote:
>   You will notice that the text control t enter the text
> for the choices is not visible.
A text control will only be shown if you set Preferences -> 
Accessibility -> "Show editors for Grid Properties".
This is due to bad support of the wxGrid implementation for screen readers.
(I did a  PR for wxWidgets to change this, but it has not yet propagated 
into wxPython.)

Normally, that's not required. You can just edit inside the grid:

Regards,

Dietmar

[wxGlade] Issue with wxGlade

[Igor K. <iko...@gm...>]

H,
There is another issue with wxGlade (latest release)

I have a dialog with wxComboBox.
Select combo box
in the "Properties" notebook select "Widgets" page.
Click the "Add" button.

 You will notice that the text control t enter the text
for the choices is not visible.

No matter how many choices I want to add..

I'm working on a regular Windows laptop and no HighDPI monitor.

Thank you.

Re: [wxGlade] Bug report

[Igor K. <iko...@gm...>]

Hi, Dietmar,

That's ok.

Thx.


On Thu, Apr 17, 2025, 9:54 AM Dietmar Schwertberger <
mai...@sc...> wrote:

> Hi Igor,
>
> thanks for reporting. I will look into this, but earliest in a week.
>
> Regards,
>
> Dietmar
>
>
>
> _______________________________________________
> wxGlade-general mailing list
> wxG...@li...
> https://lists.sourceforge.net/lists/listinfo/wxglade-general
>

Re: [wxGlade] Bug report

[Dietmar S. <mai...@sc...>]

Hi Igor,

thanks for reporting. I will look into this, but earliest in a week.

Regards,

Dietmar

[wxGlade] Bug report

[Igor K. <iko...@gm...>]

Hi, ALL,

I hit such exceptional after following this steps:

1. Start wxGlade.
2. Create extolling. Put some controls on it, including static text.
3. Leave it untouched for some time.
4. When you comeback, remove one of the control and put the wxStaticText
instead. For the new static text, check “Store as Attribute “.
5. Click on the other static text in order to set the same checkbox and you
will see a crash.

I have an old and slow system with Windows 8.1..

Thank you.



ERROR   : None
An unexpected error occurred!

Exception type:      <class 'AttributeError'>
Exception details:   'NoneType' object has no attribute 'finalize'

Application stack traceback:
  File "C:\Program Files\wxGlade-1.1.0_win_amd64\new_properties.py", line
1526, in on_kill_focus
    self.flush()
  File "C:\Program Files\wxGlade-1.1.0_win_amd64\new_properties.py", line
1578, in flush
    self._check_for_user_modification()
  File "C:\Program Files\wxGlade-1.1.0_win_amd64\new_properties.py", line
1543, in _check_for_user_modification
    ret = Property._check_for_user_modification(self, new_value, force,
activate)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Program Files\wxGlade-1.1.0_win_amd64\new_properties.py", line
184, in _check_for_user_modification
    self.on_value_edited(new_value, activate or force or None)
  File "C:\Program Files\wxGlade-1.1.0_win_amd64\new_properties.py", line
171, in on_value_edited
    common.history.property_changed(self)
  File "C:\Program Files\wxGlade-1.1.0_win_amd64\history.py", line 468, in
property_changed
    item = self._finalize_item()
           ^^^^^^^^^^^^^^^^^^^^^
  File "C:\Program Files\wxGlade-1.1.0_win_amd64\history.py", line 457, in
_finalize_item
    item.finalize(self._monitor)
    ^^^^^^^^^^^^^

Date and time:       2025-04-16T20:27:32.251437
Python version:      3.12.0
wxPython version:    4.2.1
wxWidgets platform:  __WXMSW__
wxGlade version:     1.1.0

Re: [wxGlade] Restoring saved window properties

[Dietmar S. <mai...@sc...>]

Alternatively, try adding a call to SafeYield or Yield before the sash 
positions are set:

         wx.SafeYield()
         self.splitter1.SetSashPosition( positions[0] )
         self.splitter2.SetSashPosition( positions[1] )

Regards,

Dietmar

Re: [wxGlade] Restoring saved window properties

[Dietmar S. <mai...@sc...>]

On 4/1/2025 7:23 PM, Johan Vromans wrote:
> This is what I have now:
>
>          positions = self.layout_settings["sash_positions"][new_layout]
>          self.splitter1.SetSashPosition( positions[0] )
>          self.splitter2.SetSashPosition( positions[1] )
>          if compat.IS_GTK and initial:
>              wx.CallAfter(self.splitter1.SetSashPosition, positions[0] )
>              wx.CallAfter(self.splitter2.SetSashPosition, positions[1] )
>
> Unfortunately, it does not make a difference.

OK, then maybe try replacing "wx.CallAfter(" with e.g. "wx.CallLater(200, ".

If that does not help, then I have no idea...

Regards,

Dietmar

Re: [wxGlade] Restoring saved window properties

[Johan V. <jvr...@sq...>]

On Tue, 1 Apr 2025 18:55:19 +0200, Dietmar Schwertberger wrote:

> This behaviour looks platform dependent. I could not see it on Windows 
> or my Ubuntu VM and Kubuntu installation.

I checked Fedora Rawhide and it restores the sash correctly, but it fails
to restore the window sizes :).

> Could you please try the workaround of adding these lines to main.py 
> wxGladeFrame.switch_layout?
> (around line 1400)
> 
>          if compat.IS_GTK and initial:
>              wx.CallAfter(self.splitter1.SetSashPosition, positions[0] )
>              wx.CallAfter(self.splitter2.SetSashPosition, positions[1] )

This is what I have now:

        positions = self.layout_settings["sash_positions"][new_layout]
        self.splitter1.SetSashPosition( positions[0] )
        self.splitter2.SetSashPosition( positions[1] )
        if compat.IS_GTK and initial:
            wx.CallAfter(self.splitter1.SetSashPosition, positions[0] )
            wx.CallAfter(self.splitter2.SetSashPosition, positions[1] )


Unfortunately, it does not make a difference.

Re: [wxGlade] Restoring saved window properties

[Dietmar S. <mai...@sc...>]

This behaviour looks platform dependent. I could not see it on Windows 
or my Ubuntu VM and Kubuntu installation.

Could you please try the workaround of adding these lines to main.py 
wxGladeFrame.switch_layout?
(around line 1400)

         if compat.IS_GTK and initial:
             wx.CallAfter(self.splitter1.SetSashPosition, positions[0] )
             wx.CallAfter(self.splitter2.SetSashPosition, positions[1] )

Regards,

Dietmar

Re: [wxGlade] Restoring saved window properties

[Johan V. <jvr...@sq...>]

On Mon, 31 Mar 2025 22:33:30 +0200, Dietmar Schwertberger wrote:

See my other mail.

I notice the vertical position of the left splitter is restored correctly.

Re: [wxGlade] Restoring saved window properties

[Johan V. <jvr...@sq...>]

On Mon, 31 Mar 2025 22:33:30 +0200, Dietmar Schwertberger wrote:

>  From your first post I got the impression that not even the basic 
> layout is restored.
> ("always need Alt+1 first.")

Maybe I wasn't clear, sorry for that.

I have a running wxGlade with a particular window size, layout (Layout 1,
Tree) and sash position (see attachment 1).

When I save it and restart wxglade, I get the same size for the main
window, tree view with (most of the time but not always) collapsed left
pane. The design window is at its initial size again. (attachment 2)

When I hit Alt+1, most of the time (but not always) the sash position
is restored.

Note that I need to place the design window manually, that is the Gnome?
restriction I mentioned earlier.

> Maybe you can try some debug messages at lines 1410ff in 'switch_layout' 
> where the sash positions are set:
> 
> positions = self.layout_settings["sash_positions"][new_layout] 
> print("stored or default sash_positions", positions) print("initial sash 
> positions", self.splitter1.GetSashPosition(), 
> self.splitter2.GetSashPosition()) self.splitter1.SetSashPosition( 
> positions[0] ) self.splitter2.SetSashPosition( positions[1] ) 
> print("sash positions after setting", self.splitter1.GetSashPosition(), 
> self.splitter2.GetSashPosition())

The sash positions in wxgladerc are:

sash_positions_l0_l0 = 396
sash_positions_l0_l1 = 380

wxGlade prints:

stored or default sash_positions [396, 380]
initial sash positions 10 10
sash positions after setting 13 14

The sash positions in wxgladerc are now:

sash_positions_l0_l0 = 189
sash_positions_l0_l1 = 380


It's a minor nuisance, but a nuisance nevertheless.

Re: [wxGlade] Restoring saved window properties

[Dietmar S. <mai...@sc...>]

 From your first post I got the impression that not even the basic 
layout is restored.
("always need Alt+1 first.")

Maybe you can try some debug messages at lines 1410ff in 'switch_layout' 
where the sash positions are set:

positions = self.layout_settings["sash_positions"][new_layout] 
print("stored or default sash_positions", positions) print("initial sash 
positions", self.splitter1.GetSashPosition(), 
self.splitter2.GetSashPosition()) self.splitter1.SetSashPosition( 
positions[0] ) self.splitter2.SetSashPosition( positions[1] ) 
print("sash positions after setting", self.splitter1.GetSashPosition(), 
self.splitter2.GetSashPosition())

Actually, my VM was Ubuntu, not Kubuntu, so it's probably Gnome as well.

Regards,

Dietmar

Re: [wxGlade] Restoring saved window properties

[Johan V. <jvr...@sq...>]

On Mon, 31 Mar 2025 19:16:46 +0200, Dietmar Schwertberger
<mai...@sc...> wrote:

> print("layout_info",  (x,y), (widths[0],height), layout )

Sure.

This is the relevant portion of wxgladerc:

````
[layout]
height = 1079
layout = 0
sash_positions_l0_l0 = 396
sash_positions_l0_l1 = 380
sash_positions_l1_l0 = 539
sash_positions_l1_l1 = 190
sash_positions_l2_l0 = 719
sash_positions_l2_l1 = 359
widths_l0 = 1047
widths_l1 = 500
x = 0
y = 1
````

Starting wxglade it prints

layout_info (0, 1) (1047, 1079) 0

I know that on Gnome based desktops it is not possible to control the
position of the main window. It wil allways appear at 0,0.

Setting the size of the window works correctly.

It is the sash positions that do not get restored.

Re: [wxGlade] Restoring saved window properties

[Dietmar S. <mai...@sc...>]

I have now tried in my Kubuntu VM and there the restore of the layout is 
working.

Could you please try to identify the problem?

The code is in main.py, lines 1313ff, method 'init_layout_settings'.

I would suggest to step through with a debugger or to replace
         except:
             return default_pos, default_size, 0
with
         except:
             raise
             #return default_pos, default_size, 0

and add a print before the end:

         print("layout_info",  (x,y), (widths[0],height), layout )
         return (x,y), (widths[0],height), layout  # return widths[0] as 
0 is the initial setting


Regards,

Dietmar

Re: [wxGlade] Restoring saved window properties

[Johan V. <jvr...@sq...>]

On Sun, 30 Mar 2025 18:19:22 +0200, Dietmar Schwertberger wrote:

> Not sure about this. What if there is more than one window?

When I start wxGlade the selected item is the app. Pressing F6 shows one of
the design windows. If there's one, it will be the right one.

If there are more it is not different from the current situation.