#197 Can't run wxGlade under CentOS 7

[Jonas Lindemann]

Starting wxGlade produces:

Traceback (most recent call last):
  File "wxglade.py", line 49, in <module>
    import common
  File "/home/....", line 24, in <module>
    import config, compat, plugins
  File "/home/.../compat.py", line 222, in <module>
    wx_ToolTip_SetAutoPop = wx.ToolTip_SetAutoPop
AttributeError: 'module' object has no attribute 'ToolTip_SetAutoPop'

I semi-fixed this by:

def dummy(*args): # <---
    pass

if len(wx.VERSION)==5:
    # wxPython Classic
    IS_CLASSIC = True
    IS_PHOENIX = False

    EVT_GRID_CELL_CHANGE = wx.grid.EVT_GRID_CELL_CHANGE
    wx_SystemSettings_GetFont = wx.SystemSettings_GetFont
    wx_SystemSettings_GetColour = wx.SystemSettings_GetColour
    wx_ArtProviderPush = wx.ArtProvider.PushProvider
    wx_ArtProvider_GetBitmap = wx.ArtProvider_GetBitmap
    wx_ToolTip_SetDelay = wx.ToolTip_SetDelay
    wx_ToolTip_SetAutoPop = dummy #<----
    wx_Tree_InsertItemBefore = wx.TreeCtrl.InsertItemBefore
    def SetToolTip(c, s):
        c.SetToolTipString(s)

However, I am not sure this fixes anything. wxGlade seems to crash horrible when closing. We probarbly need some better solution.

-- Jonas

[Dietmar Schwertberger]

Hi Jonas,

it's strange that SetAutoPop is not available on your installation. Replacing it with dummy should be fine, though.

I have only Windows for testing.
Would you mind testing the current version of branch DEV_DS_2016 on your installation and also with Python 3.4 or 3.5 with a recent snapshot of Phoenix?
Does the crash always occur or only when you did load and edit certain files?

Regards,

Dietmar

[Jonas Lindemann]

On 2016-11-02 21:44, Dietmar Schwertberger wrote:

Hi Jonas,

it's strange that SetAutoPop is not available on your installation.
Replacing it with dummy should be fine, though.

Ok.

I have only Windows for testing.
Would you mind testing the current version of branch DEV_DS_2016 on
your installation and also with Python 3.4 or 3.5 with a recent
snapshot of Phoenix?

I would like to be able to run it without additional installs, but I can
give it a try.

Does the crash always occur only when you did load and edit certain files?

it seems that is was the first time I started it. After restarting it
most messages went away. The error dialog is a bit annoying. Especially
if the errors can be ignored.

Otherwise I like wxGlade a lot!

-- Jonas

Regards,

Dietmar

---

*[bugs:#197] https://sourceforge.net/p/wxglade/bugs/197/ Can't run
wxGlade under CentOS 7 *

Status: open
Created: Tue Nov 01, 2016 02:21 PM UTC by Jonas Lindemann
Last Updated: Tue Nov 01, 2016 02:21 PM UTC
Owner: nobody

Starting wxGlade produces:

Traceback (most recent call last):
File "wxglade.py", line 49, in <module>
import common
File "/home/....", line 24, in <module>
import config, compat, plugins
File "/home/.../compat.py", line 222, in <module>
wx_ToolTip_SetAutoPop = wx.ToolTip_SetAutoPop
AttributeError: 'module' object has no attribute 'ToolTip_SetAutoPop'</module></module></module>

I semi-fixed this by:

def dummy(*args): # <---
pass

if len(wx.VERSION)==5:
# wxPython Classic
IS_CLASSIC = True
IS_PHOENIX = False

 EVT_GRID_CELL_CHANGE = wx.grid.EVT_GRID_CELL_CHANGE
 wx_SystemSettings_GetFont = wx.SystemSettings_GetFont
 wx_SystemSettings_GetColour = wx.SystemSettings_GetColour
 wx_ArtProviderPush = wx.ArtProvider.PushProvider
 wx_ArtProvider_GetBitmap = wx.ArtProvider_GetBitmap
 wx_ToolTip_SetDelay = wx.ToolTip_SetDelay
 wx_ToolTip_SetAutoPop = dummy #<----
 wx_Tree_InsertItemBefore = wx.TreeCtrl.InsertItemBefore
 def SetToolTip(c, s):
     c.SetToolTipString(s)

However, I am not sure this fixes anything. wxGlade seems to crash
horrible when closing. We probarbly need some better solution.

-- Jonas

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/wxglade/bugs/197/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Dietmar Schwertberger]

I would like to be able to run it without additional installs, but I can
give it a try.
If it runs, then it's fine to stay with 2.7 for a while. In case of hard C++ crashes, it's interesting to see the differences to find a workaround, but it's quite some time that I had one...
I've just updated the DEV_DS_2016 branch with a major functional upgrade.

it seems that is was the first time I started it. After restarting it
most messages went away. The error dialog is a bit annoying. Especially
if the errors can be ignored.
I don't like the current logging system either. Usually, I'm fine with printing warnings on the console and a simple backtrace in case of something major...

Regards,

Dietmar

[Carsten Grohmann]

Hi Jonas,

I've implemented the current bug report dialog to simplify the reporting the bugs.

The dialog should raised for major errors only. The dialog should never raised if the error can be ignored. That would be a fail and will be fixed.

Please report errors told by the dialog. You can open a ticket, send a mail to the mailing list or to me directly.

Regards,
Carsten

[Dietmar Schwertberger]

I just tried with a Phoenix snapshot and Python 3.5.
Startup seems to work.
For Classic, I've added your workaround.