Scheduler Mouse Crashes (vista)

Message Topic Search Topic Options Post Reply Create New Topic Printable Version


   Aurora Scheduler
OS: Vista
Behavior: Crashes when I start using my mouse

"
Debugging Information:
5: Invalid procedure call or argument
Aurora.Scheduler.CalendarMouse.0
Aurora.Scheduler.CalendarMouse.2.2Col 3Row 1Item 0Bound 0Data
"

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version
dylanwalker Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 06 Oct 2008 Online Status: Offline Posts: 15	Quote Reply Topic: Scheduler Mouse Crashes (vista) Posted: 09 Oct 2008 at 8:58am
	Aurora Scheduler OS: Vista Behavior: Crashes when I start using my mouse " Debugging Information: 5: Invalid procedure call or argument Aurora.Scheduler.CalendarMouse.0 Aurora.Scheduler.CalendarMouse.2.2Col 3Row 1Item 0Bound 0Data "

Pony_God Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 01 Sep 2008 Location: Naples, FL Online Status: Offline Posts: 551	Quote Reply Posted: 09 Oct 2008 at 9:21am
	Try a few things meantioned in the "Aurora installed, but crashes when opening" thread. We talk about the mouse crashing schedular there.
	Fine. You're so smart you rig up the lights. D-Light users Unite!

dylanwalker Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 06 Oct 2008 Online Status: Offline Posts: 15	Quote Reply Posted: 11 Oct 2008 at 2:37pm
	ponygod, I tried the thread you mentioned, however as far as I can tell there hasn't been any suggestions that relate to the mouse bug (there are several suggestions for dealing with the other problems he experiences). Maybe it would be better to pursue the scheduler mouse bug on its own thread (so as not to confuse the issue)? Some info about the mouse bug that might be relevant: 1) I am using a synaptics touchpad on my laptop 2) I am running Vista 3) My controller hardware is not connected at all (so I don't think it pertains to a COM port conflict; I also tried changing the COM port but no network ID shows up, presumably because no controller is connected).