Closed GoogleCodeExporter closed 8 years ago
Original comment by jose.exposito89@gmail.com
on 23 May 2011 at 8:50
Another idea is to mark changes in the table.
Sometimes, the combination of the scrollable gesture listing and scrollable
dropout-boxes (excuse my bad knowledge about these QT-gadgets) creates a
problem: By scrolling up and down, you may scroll the listing or pick another
Gesture/Action. And then you may not recognize the accidental changes. Can be
quite annoying. Maybe other inputs could be used.
In my opinion, the old arrangement of Touchégg-GUI v0.2 (as shown in the 2nd
video), looks more user-friendly.
Original comment by dauersurfer@gmail.com
on 23 May 2011 at 1:28
confirmed, it might help to simply disable scrolls on these boxes.
As to the buttons, is the APPLY / ACCEPT button really required? It might be
more intuitive to remove these and automatically apply any changes without
requiring additional user action.
Original comment by Linus.Seelinger
on 23 May 2011 at 3:21
Yes, the only problem is that now Touchégg has more gestures and actions and
support apps, for this reason is more dificult do this in the GUI. Anyway, I
have plans to make a widget for facilitate the gesture recognition, ie, a
window in than you can make a gesture t select it automatly (like the widget to
select shortcuts)... but for the next version ;)
Greetings!
Original comment by jose.exposito89@gmail.com
on 23 May 2011 at 3:21
That would be perfect. The GUI should be easier to handle than editing the
config file.
Original comment by dauersurfer@gmail.com
on 24 May 2011 at 10:06
Sounds good!
However, (i like playing advocatus diaboli ;) ) you'd have to be careful as
such a widget might easily be misunderstood to "record" any user-defined
gestures, instead of just selecting them...
So, somehow you should show the user all available gesture types (I liked these
graphics in the earlier GUI versions very much!)
Original comment by Linus.Seelinger
on 12 Oct 2011 at 8:51
Original comment by jose.exposito89@gmail.com
on 1 Aug 2013 at 2:33
Original issue reported on code.google.com by
dauersurfer@gmail.com
on 23 May 2011 at 8:08