[wxPython-users] wxPython 2.6.3.3 different GetDisplayID behaviour?

[Charl P. Botha]

On 10/6/06, Robin Dunn <robin at alldunn.com> wrote:
> Charl P. Botha wrote:
> > Did anything change in the behaviour of wxGetXDisplay() between
> > wxPython 2.6.2.1 and wxPython 2.6.3.3 ?
>
> No, it just returns the value of GDK_DISPLAY() in each version.  I also
> verified that the wxPython code wrapping wx.Window.GetHandle() hasn't
> changed.

Robin, have a look at this:

wxPython 2.6.2.1, Python 2.4.3
>>> import wx
>>> d = wx.GetXDisplay()
>>> print d
_10574308_p_void
>>> d.__hex__()
'8435710'
>>>

wxPython 2.6.3.3, Python 2.5
>>> import wx
>>> d = wx.GetXDisplay()
>>> print d
_783d3f08_p_void
>>> d.__hex__()
'0x83f3d78'
>>>

It seems the behaviour of the __hex__ method of the returned swig
object has changed.  Is this due to the different Python versions
(that would be strange) or due to some other change in the wxPython
wrappings?

By the way, this is the reason why VTK is currently broken on wxPython
2.6.3.3 on Linux.  I'll make a fix for this and commit to VTK CVS.

See you,
Charl