View Single Post
  #1  
Old 11-27-2007, 11:34 PM
DustyPorViva DustyPorViva is offline
Will work for food. Maybe
DustyPorViva's Avatar
Join Date: Sep 2003
Location: Maryland, USA
Posts: 9,589
DustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond reputeDustyPorViva has a reputation beyond repute
Send a message via AIM to DustyPorViva Send a message via MSN to DustyPorViva
Global mouse checks

I've encountered this problem multiple times while working with GUI's in Graal. There is no 'universal' check for mouseclicks. onMouseUp, for example, only fires when the mouse is released inside GraalControl. The main problem arises when dealing with the drag function for GUI's. Ideally, if you start a drag inside a GUI, you don't want the functionality of it to stop working just because you leave the GUI... it makes it tedious to work. If I start dragging my mouse and leave the GUI, it messes the script up, and I've yet to find a way to work around this.

Either way, functions like onMouseUp and onMouseDown should be relevant to the GUIContainer, not GraalControl.
Reply With Quote