Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#57 closed defect (fixed)

mouseMoved event doesn't always register

Reported by: cobyrne Owned by: cobyrne
Priority: major Milestone:
Component: component1 Version:
Keywords: mar6 Cc:
Blocked By: Blocking:


There seems to be some weird behavior with the mouseMoved event. It does't seem to want to register initially. And sometimes it will just stop registering. I'm very confused. I don't remember it happening in the demo though, so I'm not sure what's up...

Change History (4)

comment:1 Changed 4 years ago by cobyrne

adding the outline function actually seemed to improve this for some reason. whenever it seems to stop registering if you click the map it brings it back.

if someone else can confirm that this works, i think we can close this

comment:2 Changed 4 years ago by cobyrne

  • Owner changed from somebody to cobyrne
  • Status changed from new to assigned

This is actually a pychan bug. see;topic=260.0

mousepressed creates the context menu, then pychan takes over mouse input, but pychan doesnt generate the mousereleased event, so all new mousemoved events actually register as mousedragged events (allegedly. im about to test this)

they fixed this by changing from mousepressed to mousereleased to call the context menu. i'm about to test that as well

comment:3 Changed 4 years ago by cobyrne

  • Resolution set to fixed
  • Status changed from assigned to closed

changing it from mousepresed to mousereleased fixed the problem

comment:4 Changed 4 years ago by cobyrne

  • Keywords mar6 added
Note: See TracTickets for help on using tickets.