Bug 7872 - edge_flip_pointer what about corner flipping?
Summary: edge_flip_pointer what about corner flipping?
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: App/compiz (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high enhancement
Assignee: David Reveman
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-14 12:20 UTC by Karl Lattimer
Modified: 2009-02-03 12:06 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Karl Lattimer 2006-08-14 12:20:02 UTC
I'm currently using david the deity of accelloration's wonderful Xgl ;) After
the plug thats rightly so after my bag and cap (RE: rev. Ted) arrived, novell
novell novell, novell novell novell ;)

Anyway, I see edge_flip_dnd, edge_flip_move and edge_flip_pointer, why don't I
see corner_flip_* too, it makes more sense to have corner flipping (RF: fitts
law) than the edge, as the edge is infinite in the compiz cube it gives you
nothing to aim for. A corner would serve to guide the cursor to a point of
action, and also the corner is a place where miss hitting the edge can cause a
strange sort of motion sickness as its kinda bouncy, you're not expecting it and
it feels very accidental, not so much so with dragging and moving but with
pointer definately. 

I think corner flipping would be much more appropriate with the mouse pointer.
In fact I actually use this now with brightside and a dodgy hack;  

xte "keydown Control_L" "keydown Alt_L" "keydown Right" "keyup Right" "keyup
Alt_L" "keyup Control_L"

It would be more suitable to have this in compiz as an option.
Comment 1 Daniel Stone 2007-02-27 01:33:10 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 2 Kristian Lyngstøl 2009-02-03 12:06:12 UTC
We have corner bindings now... please re-open on bugs.opencompositing.org if that's not enough.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.