Yes. This is the intended behaviour. The idea was to establish a clear
selection region. It is interesting though to consider a trigger of
selection mode on upward pull
On 12 Mar 2013 21:00, "kevin gunn" <email address hidden> wrote:
> i noticed too that the once the commit threshold is reached, when the
> finger travels back/upward (technically back into non-
> committed/threshold), movement to the next icon isn't allowed either.
> should it be ?? it seemed odd to me.
>
> ** Changed in: manhattan
> Assignee: Michał Sawicz (saviq) => Oren Horev (oreneeshy)
>
> --
> You received this bug notification because you are a bug assignee.
> Matching subscriptions: Manhattan bugs
> https://bugs.launchpad.net/bugs/1134491
>
> Title:
> [indicators] improve the indicator selection
>
> Status in The Manhattan project:
> Confirmed
>
> Bug description:
> Still not refined enough
> Blank bar has caused some confusion.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/manhattan/+bug/1134491/+subscriptions
>
Yes. This is the intended behaviour. The idea was to establish a clear
selection region. It is interesting though to consider a trigger of
selection mode on upward pull
On 12 Mar 2013 21:00, "kevin gunn" <email address hidden> wrote:
> i noticed too that the once the commit threshold is reached, when the threshold) , movement to the next icon isn't allowed either. /bugs.launchpad .net/bugs/ 1134491 /bugs.launchpad .net/manhattan/ +bug/1134491/ +subscriptions
> finger travels back/upward (technically back into non-
> committed/
> should it be ?? it seemed odd to me.
>
> ** Changed in: manhattan
> Assignee: Michał Sawicz (saviq) => Oren Horev (oreneeshy)
>
> --
> You received this bug notification because you are a bug assignee.
> Matching subscriptions: Manhattan bugs
> https:/
>
> Title:
> [indicators] improve the indicator selection
>
> Status in The Manhattan project:
> Confirmed
>
> Bug description:
> Still not refined enough
> Blank bar has caused some confusion.
>
> To manage notifications about this bug go to:
> https:/
>