search

pbfy0 / visvis

Automatically exported from code.google.com/p/visvis
Other
0 stars 0 forks source link

Key events no longer work #19

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
VISVIS ver 1.4
Linux Mint 10
Using wxPython backend

key events are not being captured.  Try drawing example as test case

Original issue reported on code.google.com by geith.gm...@gmail.com on 14 Mar 2011 at 12:59

GoogleCodeExporter commented 9 years ago 
Can you check out revision 7acfd0eb8b54 of my clone 
(http://code.google.com/r/rschroll-visvis/)?  That solved this problem for me.

Original comment by rschr...@gmail.com on 15 Mar 2011 at 2:01

GoogleCodeExporter commented 9 years ago 
OK, Google completely screwed up those links.  Here's the revision itself: 
http://code.google.com/r/rschroll-visvis/source/detail?r=7acfd0eb8b542ff2766019a
23167a8d3d334f233

Original comment by rschr...@gmail.com on 15 Mar 2011 at 2:03

GoogleCodeExporter commented 9 years ago 
rschroll:

 Your new backend_wx.py by itself had other dependencies. 

 wx.WXK_DELETE: constants.KEY_DELETE  <<is not defined>>

File "visvis/backends/backend_wx.py", line 345, in newFigure
    figure.DrawNow()
  File "visvis/core.py", line 699, in DrawNow
    self._ProcessGuiEvents() # process all events (including our draw)
  File "visvis/backends/backend_wx.py", line 290, in _ProcessGuiEvents
    app.ProcessEvents()
  File "/visvis/events.py", line 616, in ProcessEvents
    raise NotImplemented()
TypeError: 'NotImplementedType' object is not callable

I tried adding just " self.SetFocus()"  to my original backend_wx.py but that 
alone did not work.

Do you have a modified events.py?

Thanks,
Keith

Original comment by geith.gm...@gmail.com on 15 Mar 2011 at 3:05

GoogleCodeExporter commented 9 years ago 
rschroll:

OOPS!  I take that back.  Just adding self.SetFocus() to my original 
backend_wx.py did work. (uh, my new code which is trying to catch keys isn't).

Thanks for the tip,
Keith

Original comment by geith.gm...@gmail.com on 15 Mar 2011 at 3:39

GoogleCodeExporter commented 9 years ago 
This change is now also applied to the main repo.

What a nice coincidence that you already fixed it Robert. Nice work.

Keith: Can we mark this issue as fixed? Or do you still have problems with it?

Original comment by almar.klein@gmail.com on 15 Mar 2011 at 1:03

GoogleCodeExporter commented 9 years ago 
This issue is fixed

Original comment by geith.gm...@gmail.com on 15 Mar 2011 at 3:07

GoogleCodeExporter commented 9 years ago

Original comment by almar.klein@gmail.com on 15 Mar 2011 at 3:11