You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(37) |
Aug
(66) |
Sep
(2) |
Oct
(3) |
Nov
(48) |
Dec
(65) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(12) |
Feb
(22) |
Mar
(30) |
Apr
(20) |
May
(73) |
Jun
(23) |
Jul
(44) |
Aug
(20) |
Sep
(27) |
Oct
(33) |
Nov
(30) |
Dec
(49) |
2004 |
Jan
(36) |
Feb
(31) |
Mar
(76) |
Apr
(64) |
May
(104) |
Jun
(22) |
Jul
(24) |
Aug
(49) |
Sep
(48) |
Oct
(50) |
Nov
(50) |
Dec
(47) |
2005 |
Jan
(43) |
Feb
(40) |
Mar
(19) |
Apr
(68) |
May
(21) |
Jun
(69) |
Jul
(29) |
Aug
(61) |
Sep
(57) |
Oct
(27) |
Nov
(54) |
Dec
(31) |
2006 |
Jan
(15) |
Feb
(13) |
Mar
(25) |
Apr
(18) |
May
(21) |
Jun
(7) |
Jul
(7) |
Aug
(15) |
Sep
(8) |
Oct
(44) |
Nov
(54) |
Dec
(39) |
2007 |
Jan
(34) |
Feb
(41) |
Mar
(119) |
Apr
(59) |
May
(6) |
Jun
(9) |
Jul
(18) |
Aug
(61) |
Sep
(74) |
Oct
(44) |
Nov
(23) |
Dec
(17) |
2008 |
Jan
(18) |
Feb
(21) |
Mar
(25) |
Apr
(10) |
May
(16) |
Jun
(13) |
Jul
(17) |
Aug
(7) |
Sep
(16) |
Oct
(16) |
Nov
(18) |
Dec
(4) |
2009 |
Jan
(11) |
Feb
(4) |
Mar
(4) |
Apr
(10) |
May
(18) |
Jun
(8) |
Jul
(5) |
Aug
(8) |
Sep
(9) |
Oct
(34) |
Nov
(4) |
Dec
(13) |
2010 |
Jan
(7) |
Feb
(4) |
Mar
(9) |
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
|
Oct
(14) |
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(11) |
Jun
(9) |
Jul
(12) |
Aug
(18) |
Sep
(3) |
Oct
(1) |
Nov
(6) |
Dec
(23) |
2012 |
Jan
(11) |
Feb
(13) |
Mar
(17) |
Apr
(10) |
May
(13) |
Jun
(10) |
Jul
(6) |
Aug
|
Sep
(3) |
Oct
(3) |
Nov
(5) |
Dec
(4) |
2013 |
Jan
(6) |
Feb
(3) |
Mar
(26) |
Apr
(14) |
May
|
Jun
(3) |
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(7) |
2014 |
Jan
(2) |
Feb
|
Mar
|
Apr
(9) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(3) |
Sep
(1) |
Oct
(22) |
Nov
(8) |
Dec
(2) |
2015 |
Jan
(9) |
Feb
(7) |
Mar
(5) |
Apr
(5) |
May
(4) |
Jun
(5) |
Jul
|
Aug
(11) |
Sep
(2) |
Oct
(19) |
Nov
(14) |
Dec
(6) |
2016 |
Jan
(5) |
Feb
(30) |
Mar
(7) |
Apr
(5) |
May
(13) |
Jun
(2) |
Jul
|
Aug
|
Sep
(10) |
Oct
(3) |
Nov
(8) |
Dec
(3) |
2017 |
Jan
(8) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
|
Jun
(7) |
Jul
(6) |
Aug
|
Sep
(6) |
Oct
(18) |
Nov
(31) |
Dec
(1) |
2018 |
Jan
(10) |
Feb
(4) |
Mar
(3) |
Apr
(5) |
May
(10) |
Jun
(3) |
Jul
(8) |
Aug
|
Sep
|
Oct
(6) |
Nov
(18) |
Dec
(15) |
2019 |
Jan
(61) |
Feb
(11) |
Mar
(27) |
Apr
(43) |
May
(12) |
Jun
(13) |
Jul
(18) |
Aug
(19) |
Sep
(16) |
Oct
(7) |
Nov
|
Dec
|
2020 |
Jan
(6) |
Feb
(4) |
Mar
|
Apr
(24) |
May
(1) |
Jun
(6) |
Jul
(22) |
Aug
(8) |
Sep
(40) |
Oct
(1) |
Nov
(1) |
Dec
(2) |
2021 |
Jan
(10) |
Feb
(3) |
Mar
(2) |
Apr
(7) |
May
(10) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
(13) |
Feb
(11) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(18) |
Sep
(3) |
Oct
|
Nov
(30) |
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
(19) |
May
(7) |
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
(5) |
Dec
(6) |
From: ChordPro T. <in...@ch...> - 2022-02-04 11:03:25
|
Hi Dietmar, Thanks for the suggestions. On Thu, 3 Feb 2022 18:49:53 +0100, Dietmar Schwertberger wrote: > I think that this is one of the cases where a later call to 'SetStyle' > will not work. Assuming you mean 'SetWindowStyle', yes. > You may either "simulate" a readonly text ctrl or replace it. Replacing has the disadvantage that you need to transfer tooltips and events as well. > Try code like this in "Code to inserted after": I set the widget style to wxTE_READONLY and (remember, this is Perl) this 'insert after' code: if ( $^O =~ /darwin/ ) { $self->{t_configfiledialog}->Destroy; $self->{t_configfiledialog} = Wx::TextCtrl->new($self, wxID_ANY, ""); } The generated code then becomes: $self->{t_configfiledialog} = Wx::TextCtrl->new($self, wxID_ANY, "", wxDefaultPosition, wxDefaultSize, wxTE_READONLY); $self->{t_configfiledialog}->SetToolTipString(_T("...tooltip...")); if ( $^O =~ /darwin/ ) { $self->{t_configfiledialog}->Destroy; $self->{t_configfiledialog} = Wx::TextCtrl->new($self, wxID_ANY, ""); } $self->{sz_configfile}->Add($self->{t_configfiledialog}, 1, wxEXPAND, 0); This should work, events are attached later, but as you can see the tooltip is already set so this needs to be copied. Okay, that is doable. > Alternatively, you could use a CustomWidget. > > - instance class: TextCtrl > - Arguments: $parent, $id, style=style > - Code to be inserted before: style = wx.TE_READONLY if > sys.platform=="darwin" else 0 Even though you prefer the other alternatives, I like this one. However, the instance class dialog (when creating the widget) does not accept Perl syntax for the class. When entering "wxTextCtrl" it ends up as "wxTextCtrl" in the code while for the built-in widgets this is automatically converted to "Wx::TextCtrl" when generating Perl. Not a real problem since the class name can be changed in the Common Instance class text field. In the Widget tab the following arguments - $parent - $id - "" - wxDefaultPosition - wxDefaultSize - $^O =~ /darwin/ ? 0 : wxTE_READONLY Seems to work fine. Note that entering "" (that's two &dquot;s) in the arguments in the Widget tab yields an error dialog (see at end) that apparently does no (real) harm. Great job, thanks! ----error details---- ERROR : None An unexpected error occurred! Exception type: <class 'AttributeError'> Exception details: 'NoneType' object has no attribute 'finalize' Application stack traceback: File "/home/jv/wrk/wxGlade/wxGlade/new_properties.py", line 2947, in on_cell_changed self._on_value_edited(row, col, value) # this can add a row File "/home/jv/wrk/wxGlade/wxGlade/new_properties.py", line 2978, in _on_value_edited common.history.property_changed(self) File "/home/jv/wrk/wxGlade/wxGlade/history.py", line 445, in property_changed item = self._finalize_item() File "/home/jv/wrk/wxGlade/wxGlade/history.py", line 434, in _finalize_item item.finalize(self._monitor) Date and time: 2022-02-04T11:36:53.738036 Python version: 3.9.9 wxPython version: 4.0.7 wxWidgets platform: __WXGTK__ wxGlade version: 1.1.0pre ----end---- |
From: Dietmar S. <mai...@sc...> - 2022-02-03 18:24:45
|
Alternatively, you could use a CustomWidget. - instance class: TextCtrl - Arguments: $parent, $id, style=style - Code to be inserted before: style = wx.TE_READONLY if sys.platform=="darwin" else 0 I would go for the first solution, though. Regards, Dietmar |
From: Dietmar S. <mai...@sc...> - 2022-02-03 17:50:12
|
On 03.02.2022 10:02, ChordPro Team wrote: > The best I have found so far is to call its SetEditable method to change > its editable status, but that doesn't change the difference in style between > a wxTE_READONLY widget and a normal one. > > Is there a decent and reliable way to accompish this? I think that this is one of the cases where a later call to 'SetStyle' will not work. You may either "simulate" a readonly text ctrl or replace it. Try code like this in "Code to inserted after": self.text_ctrl_1.DestroyLater() self.text_ctrl_1 = wx.TextCtrl(self.panel_1, wx.ID_ANY, "", style=wx.RE_READONLY) wxGlade will then generate code like this: self.text_ctrl_1 = wx.TextCtrl(self.panel_1, wx.ID_ANY, "") self.text_ctrl_1.DestroyLater() # Destroy() might be fine as well self.text_ctrl_1 = wx.TextCtrl(self.panel_1, wx.ID_ANY, "", style=wx.RE_READONLY) sizer_1.Add(self.text_ctrl_1, 0, 0, 0) If you need to do the style change later, you can retrieve the sizeritem and replace the widget. Regards, Dietmar |
From: ChordPro T. <in...@ch...> - 2022-02-03 09:19:06
|
Hi, I have a TextCtrl that I want to be wxTE_READONLY but only when the program is run on MacOS. The best I have found so far is to call its SetEditable method to change its editable status, but that doesn't change the difference in style between a wxTE_READONLY widget and a normal one. Is there a decent and reliable way to accompish this? Thanks. |
From: M A <tea...@gm...> - 2022-01-30 21:53:13
|
Sounds like a good idea. > On Jan 29, 2022, at 11:16 AM, Dietmar Schwertberger <mai...@sc...> wrote: > > Hi! > > I'm thinking about changing event binding code that is generated by wxGlade. > This is to fix issues like #507: https://github.com/wxGlade/wxGlade/issues/507 > The problem there is that non-command events like mouse events do not propagate to the surrounding container. > Also, in a future release I would like to add an easier way for the user to specify arbitrary events and so more non-command events will be used. > > In general, this requires to bind the event handler to the widget, not the surrounding frame. > E.g. current code: > > self.Bind(wx.EVT_BUTTON, self.on_button_event, self.button) > > > # this won't work as the event does not propagate: > > > self.Bind(wx.EVT_LEFT_DOWN, self.on_button_mouse_event, self.button) > > New code: > > self.button.Bind(wx.EVT_BUTTON, self.on_button_event) self.button.Bind(wx.EVT_LEFT_DOWN, self.on_button_mouse_event) > > Does anybody have objections? > For now I will only change this for Python. > I don't know whether Lisp would support the change. > For Perl it would probably work. If someone volunteers for testing, I will implement the change. > > For C++ at the moment still event tables are generated. It's time to change this, but again I need a volunteer. > > Regards, > > Dietmar > _______________________________________________ > wxGlade-general mailing list > wxG...@li... > https://lists.sourceforge.net/lists/listinfo/wxglade-general |
From: Dietmar S. <mai...@sc...> - 2022-01-29 16:16:53
|
Hi! I'm thinking about changing event binding code that is generated by wxGlade. This is to fix issues like #507: https://github.com/wxGlade/wxGlade/issues/507 The problem there is that non-command events like mouse events do not propagate to the surrounding container. Also, in a future release I would like to add an easier way for the user to specify arbitrary events and so more non-command events will be used. In general, this requires to bind the event handler to the widget, not the surrounding frame. E.g. current code: | self.Bind(wx.EVT_BUTTON, self.on_button_event, self.button)| |||||||||# this won't work as the event does not propagate:|| |||self.Bind(wx.|||||EVT_LEFT_DOWN|, self.on_button_mouse_event, self.button)|| || ||New code: | ||||||| self.button||||.Bind(wx.EVT_BUTTON, self.on_button_event)|||||self.button.Bind(wx.|||||EVT_LEFT_DOWN|, self.on_button_mouse_event) ||| ||| ||| |||Does anybody have objections?||| |||For now I will only change this for Python.||| |||I don't know whether Lisp would support the change.||| |||For Perl it would probably work. If someone volunteers for testing, I will implement the change.||| |||||| |||For C++ at the moment still event tables are generated. It's time to change this, but again I need a volunteer.||| |||||| |||Regards,||| |||Dietmar|||||||| | |
From: <cry...@gm...> - 2022-01-07 13:54:31
|
OK, but here is my use model which, I think, shows why you would do it. I have multiple listctrl’s each on a separate tab in a notebook. For each list there is a fixed set of operations I want to occur on a right click. So I would have listctrl_a with popup_a listctrl_b with popup_b … A separate class for each of the popups. Now I can certainly do that manually and build everything out, but it seemed like a natural fit for wxGlade. Thanks for the response and now on to coding 😊 David From: Dietmar Schwertberger <mai...@sc...> Sent: Friday, January 7, 2022 6:22 AM To: wxg...@li... Subject: Re: [wxGlade] Popup menu in wxGlade On 07.01.2022 05:14, David Grawrock wrote: I’d like to manage the popup menu in wxGlade but the only choice I appear to have is the MenuBar. I don’t see any options to change the menubar into a simple menu. Does this have to be done manually? Am I missing something? No, there's no popup menu support in wxGlade. Popup menus should be dynamic / context sensitive. So probably it would not help too much to have an editor for a static menu. Regards, Dietmar |
From: Dietmar S. <mai...@sc...> - 2022-01-07 13:21:49
|
On 07.01.2022 05:14, David Grawrock wrote: > > I’d like to manage the popup menu in wxGlade but the only choice I > appear to have is the MenuBar. I don’t see any options to change the > menubar into a simple menu. Does this have to be done manually? Am I > missing something? > No, there's no popup menu support in wxGlade. Popup menus should be dynamic / context sensitive. So probably it would not help too much to have an editor for a static menu. Regards, Dietmar |
From: David G. <dav...@ho...> - 2022-01-07 04:14:31
|
I'd like to manage the popup menu in wxGlade but the only choice I appear to have is the MenuBar. I don't see any options to change the menubar into a simple menu. Does this have to be done manually? Am I missing something? David Grawrock, CG(r) *The words Certified Genealogist and designation CG are registered certification marks of the Board for Certification of Genealogists, used under license by Board-certified genealogists after periodic competency evaluation, and the board name is registered in the US Patent & Trademark Office.* |
From: <cry...@gm...> - 2022-01-04 16:19:12
|
Who needs reproducible? I mean it works for now 😊 Yeah, I'll change that to do the conversions myself. David -----Original Message----- From: Dietmar Schwertberger <mai...@sc...> Sent: Tuesday, January 4, 2022 8:36 AM To: wxg...@li... Subject: Re: [wxGlade] Virtual wxListCtrl On 04.01.2022 16:05, cry...@gm... wrote: > I'm using Append and send in the whole list for the item. I do that in a loop. It seems to be a very happy camper and nicely displays the number just as I sent it (float rounded to two decimals and the ints). > > I didn't know it wasn't supposed to work 😊 Well, I rarely use the ListCtrl and did not know or use the Append method. I have just tried and here for a float I get str or repr with no rounding. So if you want reproducible behaviour, you probably should convert to string yourself anyway. Regards, Dietmar _______________________________________________ wxGlade-general mailing list wxG...@li... https://lists.sourceforge.net/lists/listinfo/wxglade-general |
From: Dietmar S. <mai...@sc...> - 2022-01-04 15:36:09
|
On 04.01.2022 16:05, cry...@gm... wrote: > I'm using Append and send in the whole list for the item. I do that in a loop. It seems to be a very happy camper and nicely displays the number just as I sent it (float rounded to two decimals and the ints). > > I didn't know it wasn't supposed to work 😊 Well, I rarely use the ListCtrl and did not know or use the Append method. I have just tried and here for a float I get str or repr with no rounding. So if you want reproducible behaviour, you probably should convert to string yourself anyway. Regards, Dietmar |
From: <cry...@gm...> - 2022-01-04 15:05:49
|
I'm using Append and send in the whole list for the item. I do that in a loop. It seems to be a very happy camper and nicely displays the number just as I sent it (float rounded to two decimals and the ints). I didn't know it wasn't supposed to work 😊 David -----Original Message----- From: Dietmar Schwertberger <mai...@sc...> Sent: Tuesday, January 4, 2022 3:08 AM To: wxg...@li... Subject: Re: [wxGlade] Virtual wxListCtrl On 04.01.2022 06:00, cry...@gm... wrote: > Second question, why does going virtual require you to return a > string? You can put a number in with the regular listctrl but virtual requires the On.. > to return a string. I can handle it ok, but just wondering why. How do you put a number into the list? 'SetItem' does only accept strings. Regards, Dietmar _______________________________________________ wxGlade-general mailing list wxG...@li... https://lists.sourceforge.net/lists/listinfo/wxglade-general |
From: Dietmar S. <mai...@sc...> - 2022-01-04 10:08:44
|
On 04.01.2022 06:00, cry...@gm... wrote: > Second question, why does going virtual require you to return a string? You > can put a number in with the regular listctrl but virtual requires the On.. > to return a string. I can handle it ok, but just wondering why. How do you put a number into the list? 'SetItem' does only accept strings. Regards, Dietmar |
From: <cry...@gm...> - 2022-01-04 05:01:00
|
Thanks that got me past the build problem. Second question, why does going virtual require you to return a string? You can put a number in with the regular listctrl but virtual requires the On.. to return a string. I can handle it ok, but just wondering why. David -----Original Message----- From: Dietmar Schwertberger <mai...@sc...> Sent: Sunday, January 2, 2022 2:12 PM To: wxg...@li... Subject: Re: [wxGlade] Virtual wxListCtrl Sorry, somehow I read 'Grid' instead of 'List'. On the Properties "Common" tab, there's an item "Instance class". There you can provide the name of your implementation with the 'On..' methods. Still, on the code tab you need to provide the required import code. Please provide feedback if you have problems. Regards, Dietmar _______________________________________________ wxGlade-general mailing list wxG...@li... https://lists.sourceforge.net/lists/listinfo/wxglade-general |
From: Dietmar S. <mai...@sc...> - 2022-01-02 21:11:57
|
Sorry, somehow I read 'Grid' instead of 'List'. On the Properties "Common" tab, there's an item "Instance class". There you can provide the name of your implementation with the 'On..' methods. Still, on the code tab you need to provide the required import code. Please provide feedback if you have problems. Regards, Dietmar |
From: Dietmar S. <mai...@sc...> - 2022-01-01 21:50:17
|
On 01.01.2022 22:08, David Grawrock wrote: > > When I mark a listctrl as being virtual, the generated code doesn’t > have anything for the columns, nor can I figure out how to create the > extra class to handle the virtual On… stubs. How do you create the > extra class? > Have e.g. a look at the wxPython demo GridHugeTable.py at https://github.com/wxWidgets/Phoenix/blob/master/demo/GridHugeTable.py There you have a class HugeTable that will provide contents and also the dimensions (via GetNumberRows / GetNumberCols). You need to implement a class like this for your data, probably in a separate file. Then create an instance, e.g. 'self.table = HugeTable()' and call 'self.my_grid.SetTable(self.my_table, True)' You can add the import and instantiation code to the "Code" properties inside wxGlade. Regards and a happy new year, Dietmar |
From: David G. <dav...@ho...> - 2022-01-01 21:08:57
|
When I mark a listctrl as being virtual, the generated code doesn't have anything for the columns, nor can I figure out how to create the extra class to handle the virtual On... stubs. How do you create the extra class? David Grawrock, CG(r) *The words Certified Genealogist and designation CG are registered certification marks of the Board for Certification of Genealogists, used under license by Board-certified genealogists after periodic competency evaluation, and the board name is registered in the US Patent & Trademark Office.* |
From: Dietmar S. <mai...@sc...> - 2021-05-21 18:24:49
|
On 21.05.2021 19:40, M A wrote: > Sounds like a "Clear File History" menu item is needed. The workaround would be to use the preferences dialog reduce the number of entries, re-start and increase again. Pull requests for improvements are welcome. Regards, Dietmar |
From: M A <tea...@gm...> - 2021-05-21 17:41:08
|
Sounds like a "Clear File History" menu item is needed. > On May 21, 2021, at 2:54 AM, William Luitje <wvl...@gm...> wrote: > > I recently had an intense period of experimenting with wxGlade to find out the best way to create the UI for a new project. I had a different wxg file for each approach so that I could try different things and go back and forth between various ideas. That worked out just fine and I was able to create the UI I wanted but then I had more than 10 wxg files in my project list in wxGlade and I knew I was not going to need to use most of them ever again. > > So I decided to see if I could find where the recent file list is stored and whether I could edit it. The answer for Windows is that it is contained in a file called file_history.txt which is stored in the directory > > C:\Users\<user_name>\AppData\Roaming\wxglade > > file_history.txt is a plain text file with one file name per line (which is terminated with a LF) and can be modified easily with a text editor. (Obviously, save a copy before modifying it, just in case.) > _______________________________________________ > wxGlade-general mailing list > wxG...@li... > https://lists.sourceforge.net/lists/listinfo/wxglade-general |
From: William L. <wvl...@gm...> - 2021-05-21 06:55:06
|
I recently had an intense period of experimenting with wxGlade to find out the best way to create the UI for a new project. I had a different wxg file for each approach so that I could try different things and go back and forth between various ideas. That worked out just fine and I was able to create the UI I wanted but then I had more than 10 wxg files in my project list in wxGlade and I knew I was not going to need to use most of them ever again. So I decided to see if I could find where the recent file list is stored and whether I could edit it. The answer for Windows is that it is contained in a file called file_history.txt which is stored in the directory C:\Users\<user_name>\AppData\Roaming\wxglade file_history.txt is a plain text file with one file name per line (which is terminated with a LF) and can be modified easily with a text editor. (Obviously, save a copy before modifying it, just in case.) |
From: Johan V. <jvr...@sq...> - 2021-05-13 06:33:02
|
On Wed, 12 May 2021 22:03:07 +0200, Dietmar Schwertberger wrote: > Well, I moved from PERL to Python around 1995 or 1996. Then you have missed all the fun stuff :). > Maybe you should give Python a chance... Occasionally I participate in some Python applications so I know Python as well. They have done a great job in copying most of Perl's interesting features. And I've known both Larry and Guido personally :). But I have a lifetime relation with Perl and no intentions to drop it anytime soon. > Anyway, as my PERL experience is far away, I can't guarantee that the > generated PERL code is correct. So please always test beta versions when > the come out. Myself, I'm only testing the generated Python code. Fair enough. I should pay more attention. Thanks, Johan |
From: Dietmar S. <mai...@sc...> - 2021-05-12 20:03:34
|
On 12.05.2021 19:54, Johan Vromans wrote: > Ok, an extra Layout() call doesn't matter much... Probably not. > though I get the feeling that I'm the only one in the world building perl > GUI applications... Well, I moved from PERL to Python around 1995 or 1996. Maybe you should give Python a chance... Anyway, as my PERL experience is far away, I can't guarantee that the generated PERL code is correct. So please always test beta versions when the come out. Myself, I'm only testing the generated Python code. Regards, Dietmar |
From: Johan V. <jvr...@sq...> - 2021-05-12 17:54:59
|
On Wed, 12 May 2021 19:27:05 +0200, Dietmar Schwertberger wrote: > Have a look at the "code before" and "code after" properties. > You should be able to achieve most things using these Yes, I played with these and they seem quite useful. However my gut feeling is that "code after" would better be placed before the call to Layout() so I can e.g. reconfigure sizers depending on proram options. Ok, an extra Layout() call doesn't matter much... My kindest thanks for continuing development and support of wxGlade, including the perl codegen. I use wxGlade for all my GUI applications even though I get the feeling that I'm the only one in the world building perl GUI applications... Regards and stay healthy. -- Johan |
From: Dietmar S. <mai...@sc...> - 2021-05-12 17:27:28
|
On 12.05.2021 19:14, Johan Vromans wrote: > I have several programs that actually use overloading of __set_properties > and/or __do_layout. I have to carefully investigate all of them to make > sure the code currently in the overloads can be safely moved to the 'new' > method. Have a look at the "code before" and "code after" properties. You should be able to achieve most things using these and maybe overloading the __init__ method. > Actually I took me by surprise... Some tools were malfunctioning and it > took a while before I started to suspect the generated code. > > It's mostly my own fault... Should have read the release notes before > upgrading wxGlade. > > I do agree that it is better to get rid of __set_properties and __do_layout. Thanks. I never liked the separation as no human being would create such code. The new code is readable, is working well with "code before" and "code after" and it's also working with screen readers. Regards, Dietmar |
From: Johan V. <jvr...@sq...> - 2021-05-12 17:14:37
|
On Wed, 12 May 2021 17:59:38 +0200, Dietmar Schwertberger wrote: > What functionality are you missing? I have several programs that actually use overloading of __set_properties and/or __do_layout. I have to carefully investigate all of them to make sure the code currently in the overloads can be safely moved to the 'new' method. Actually I took me by surprise... Some tools were malfunctioning and it took a while before I started to suspect the generated code. It's mostly my own fault... Should have read the release notes before upgrading wxGlade. I do agree that it is better to get rid of __set_properties and __do_layout. Thanks, Johan |