sorry if there is already any answer but I haven’t found anything. The problem is that when I click into empty wx.SearchCtrl (only with grey ‘Search’ text) and start to type, the ‘search’ text is still there and ruins the search, of course. I have Ubuntu 12.04 and quite recent build of wxPython 2.9.4. I have no such problems with 2.8.12.
sorry if there is already any answer but I haven't found anything. The
problem is that when I click into empty wx.SearchCtrl (only with grey
'Search' text) and start to type, the 'search' text is still there and
ruins the search, of course. I have Ubuntu 12.04 and quite recent build
of wxPython 2.9.4. I have no such problems with 2.8.12.
Does the SearchCtrl sample in the demo also behave that way? It is working for me here, although that is with my current 2.9.5 workspace.
sorry if there is already any answer but I haven’t found anything. The
problem is that when I click into empty wx.SearchCtrl (only with grey
‘Search’ text) and start to type, the ‘search’ text is still there and
ruins the search, of course. I have Ubuntu 12.04 and quite recent build
of wxPython 2.9.4. I have no such problems with 2.8.12.
Does the SearchCtrl sample in the demo also behave that way? It is
working for me here, although that is with my current 2.9.5 workspace.
Yes, it’s the same. I use self-compiled 2.9.4.0 gtk2 (classic). Should I try to compile the most recent version? Do you think there are any relevant changes?
Thanks,
Anna
···
On Wednesday, May 22, 2013 2:21:44 AM UTC+2, Robin Dunn wrote:
Does the SearchCtrl sample in the demo also behave that way? It is
working for me here, although that is with my current 2.9.5 workspace.
Yes, it's the same. I use self-compiled 2.9.4.0 gtk2 (classic). Should I
try to compile the most recent version? Do you think there are any
relevant changes?
There have been several changes for that source module, so it is likely that one of them fixed this issue.
···
On Wednesday, May 22, 2013 2:21:44 AM UTC+2, Robin Dunn wrote: