Messages

1

Suggestions / Re: User Interface (UI) suggestions

« on: October 20, 2012, 12:59:54 am »

150 miliSeconds appear to be not enough for me  but 300 do the job just fine 
but with a small issue: on fast wide scrollings it can cancel scrolling and that results in a screen blinking. I think the pixel tolerance can help to avoid such things and will make scrolling really user friendly and flexible (with battleScrollButtonPixelTolerancy and battleScrollButtonTimeTolerancy ints).

2

Programming / Re: DogfightState development

« on: October 20, 2012, 12:05:46 am »

Can't wait for minimization to be implemented 

I can play DOS version, to provide save with 5 aircrafts chasing an ufo (or maybe another situation). If this still can help - just let me know 

3

Suggestions / Re: User Interface (UI) suggestions

« on: October 19, 2012, 11:56:19 pm »

I've implemented the time-limit to the right-mouse scrolling. (not yet Pull-requested)

Cool! But I want to see how it works now. Is there a way to download updated version to test it?

But now i'm thinking, that does it make sense to make a pixel-tolerance also? Do we really need it in combination of the time-limit?

Don't know without testing of how it works now...
Maybe wide fast scrollings will be miss-interpreted by current algorithm... 

1) When too much pixels scrolled, it handles as scroll, and can not be revoked. (not affected by time of the mouse-down)

Exactly what I meant in previous posts, but don't know if it is still necessary in regard of current time criteria...

4

Suggestions / Re: User Interface (UI) suggestions

« on: October 17, 2012, 11:14:15 pm »

Maybe it would be more user friendly to make something like this:
2 = RMB Scroll + Auto Scroll, 3 = Middle MB Scroll + Auto Scroll

5

Suggestions / Re: User Interface (UI) suggestions

« on: October 15, 2012, 12:52:48 pm »

Wow!
Guys, its the fastest response I have ever seen!
Respect!

But as of original issue with right-button scrolling:
As adding of some movement threshold appears to be a good idea - then we need some criteria to differentiate two user actions (scrolling and cancelling).
I suggest to use the time between MouseDown and MouseUp events in addition to movement threshold.
Cancel action usually takes much less time than scrolling. So some constant in miliseconds can help...

Thus:
1. Cancel action - mouse can be moved slightly, but click must be fast;
2. Scrolling action - all other cases (right-button held or mouse moved greatly).