From kde-panel-devel Tue Oct 14 17:53:18 2014 From: Andrew Lake Date: Tue, 14 Oct 2014 17:53:18 +0000 To: kde-panel-devel Subject: Re: Auto-hiding panels Message-Id: X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=141330923929686 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============8374154282220071949==" --===============8374154282220071949== Content-Type: multipart/alternative; boundary=001a11c156d430dbe5050565b2e4 --001a11c156d430dbe5050565b2e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Oct 14, 2014 at 6:51 AM, =C3=80lex Fiestas wrote: > On Tuesday 14 October 2014 10:43:42 Martin Klapetek wrote: > > I'd like to change this for Plasma panels to not have any resistance or > > very minimal one, basically get it into a state that slamming the mouse > > against a screen edge will show the panel easily, without requiring an > > additional push. > I think we should ask VDG about this, it is a change in behavior and look > and > feel after all! > > Maybe just tweak to the edge triggering code might get us there as Martin suggests. :-) Best I can tell, the behavioral model from the user side is to move the cursor far enough beyond the edge and the panel will appear. Based on that behavioral model, I think the expectation would be that if the cursor is moving relatively quickly when it get's to the edge it'll get to the magic distance beyond the edge more quickly than if the cursor is moving relatively slowly. Another potential behavioral model could be a force model, where the panel unhides when the edge is hit with a certain degree of "force". Force based models can be quite complex though since it usually requires some kind of elastic resistance at the edge to allow triggering when moving the cursor relatively slowly. Also, since there are very few uses of the cursor within the screen boundaries that employ a force model, the user needs to maintain quite different behavioral models of the the cursor behavior at the edge versus the middle of the screen. It doesn't mean it can't be done, but I think it can be quite tricky to do well. A simple magic distance past the edge behavior is usually much simpler and more predictable I think and should handle the fast versus slow edge approaches just fine. Hope this helps, Andrew --001a11c156d430dbe5050565b2e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Tue, Oct 14, 2014 at 6:51 AM, =C3=80lex Fiestas wrote:
On Tuesday 14 October 2014 10:43:42 Martin Klapetek wro= te:
> I'd like to change this for Plasma panels = to not have any resistance or
> very minimal one, basically get it into a state that slamming the mous= e
> against a screen edge will show the panel easily, without requiring an=
> additional push.
I think we should ask VDG about this, it is a change in behavior and= look and
feel after all!

Maybe just tweak to the edge trigg= ering code might get us there as Martin suggests. :-)

<= div>Best I can tell, the behavioral model from the user side is to move the= cursor far enough beyond the edge and the panel will appear. Based on that= behavioral model, I think the expectation would be that if the cursor is m= oving relatively quickly when it get's to the edge it'll get to the= magic distance beyond the edge more quickly than if the cursor is moving r= elatively slowly.

Another potential behavioral mod= el could be a force model, where the panel unhides when the edge is hit wit= h a certain degree of "force". Force based models can be quite co= mplex though since it usually requires some kind of elastic resistance at t= he edge to allow triggering when moving the cursor relatively slowly. Also,= since there are very few uses of the cursor within the screen boundaries t= hat employ a force model, the user needs to maintain quite different behavi= oral models of the the cursor behavior at the edge versus the middle of the= screen. It doesn't mean it can't be done, but I think it can be qu= ite tricky to do well. A simple magic distance past the edge behavior is us= ually much simpler and more predictable I think and should handle the fast = versus slow edge approaches just fine.

Hope th= is helps,
Andrew
--001a11c156d430dbe5050565b2e4-- --===============8374154282220071949== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel --===============8374154282220071949==--