On Thursday 11 February 2016 11:23:34 Dirk Hohndel wrote:
> - make the handles see through so they don't completely obscure what's
> behind
> - only show them if there is a menu (we currently don't have a context
> menu, but the right handle still shows up
merged in master, with the two sugges
> On Feb 11, 2016, at 11:57 AM, Marco Martin wrote:
>>
>> Somewhat unrelated... the issue with the content "behind" the handles and
>> the ActionButton. I hate the idea of having a margin at the bottom (that
>> basically creates another menu bar that isn't usable for the content of my
>> app scr
On Thursday 11 February 2016 11:23:34 Dirk Hohndel wrote:
> OK, I played with this. I have a few ideas how to make things better and
> increase the likelihood that people enjoy this version:
>
> - make the handles see through so they don't completely obscure what's
> behind
+1
> - only show the
On Thu, Feb 11, 2016 at 12:01:54PM +0100, Marco Martin wrote:
> On Tuesday 09 February 2016 10:48:18 Dirk Hohndel wrote:
> > > 2) Humans' first reaction to change is always hostility (unless they are
> > > disciples of the Cult of Apple, that is).
> >
> > True. That said, I have now tried to use
> On Feb 11, 2016, at 3:01 AM, Marco Martin wrote:
>
> On Tuesday 09 February 2016 10:48:18 Dirk Hohndel wrote:
>>> 2) Humans' first reaction to change is always hostility (unless they are
>>> disciples of the Cult of Apple, that is).
>>
>> True. That said, I have now tried to use this for se
On Tuesday 09 February 2016 10:48:18 Dirk Hohndel wrote:
> > 2) Humans' first reaction to change is always hostility (unless they are
> > disciples of the Cult of Apple, that is).
>
> True. That said, I have now tried to use this for several weeks (after our
> first conversation about this which
On Tuesday 09 February 2016 21:15:28 Kai Uwe Broulik wrote:
>
> I don't recall whether our Page is scrollable automatically or you have to
> explicitly place a ScrollView there. In the latter case I don't know how we
> could automatically ensure it works properly.
it's a thing i was a bit on the
> Well, in any case, it has to be possible to permanently scroll the last item
> of a list above the action button, regardless of any property setting.
> Otherwise it would simply be broken, no matter how we change the action
> button
> behavior (as it would always be partially covered by the b
On Tue, Feb 09, 2016 at 06:00:58PM +0100, Marco Martin wrote:
> > That isn't useful in the way it's implemented right now, though. I can
> > pull it up but it springs right back. So if my list has a "tap to open an
> > item" feature, it is /really/ hard to open the last entry in that list
> > (that
On Tue, Feb 09, 2016 at 06:43:34PM +0100, Thomas Pfeiffer wrote:
> > > I understand your user's problems, however. Even though in fact, the
> > > lowest
> > > list item can still be reached by scrolling it up (a standard function
> > > supported by the list component allows users to scroll the firs
On Dienstag, 9. Februar 2016 08:13:39 CET Dirk Hohndel wrote:
> On Tue, Feb 09, 2016 at 05:04:44PM +0100, Thomas Pfeiffer wrote:
> > Yes, as Marco said, this change was a result form user testing. Two of
> > five
> > users I've tested with so far have tried swiping anywhere on the Action
> > Button
On Dienstag, 9. Februar 2016 18:00:58 CET Marco Martin wrote:
> On Tuesday 09 February 2016 08:13:39 Dirk Hohndel wrote:
> > On Tue, Feb 09, 2016 at 05:04:44PM +0100, Thomas Pfeiffer wrote:
> > > Yes, as Marco said, this change was a result form user testing. Two of
> > > five
> > > users I've test
On Tuesday 09 February 2016 08:13:39 Dirk Hohndel wrote:
> On Tue, Feb 09, 2016 at 05:04:44PM +0100, Thomas Pfeiffer wrote:
> > Yes, as Marco said, this change was a result form user testing. Two of
> > five
> > users I've tested with so far have tried swiping anywhere on the Action
> > Button's ro
On Tue, Feb 09, 2016 at 05:04:44PM +0100, Thomas Pfeiffer wrote:
>
> Yes, as Marco said, this change was a result form user testing. Two of five
> users I've tested with so far have tried swiping anywhere on the Action
> Button's row to open the drawers, because they expected it to work that way
On Tue, Feb 09, 2016 at 08:01:23AM -0800, Dirk Hohndel wrote:
>
> Current Subsurface-mobile APKs are based on a forked version of
> mobilecomponents (again) which implement just that.
Oops, crossed email. I'll switch back to master :-)
Thanks
/D
___
P
On Dienstag, 9. Februar 2016 12:06:37 CET Marco Martin wrote:
> On Monday 08 February 2016 11:48:24 Dirk Hohndel wrote:
> > I'm running into a pretty significant issues with the ActionButton:
> >
> > Its MouseArea has an implicitWidth of parent.width. Which means that my
> > page will not receive
On Tue, Feb 09, 2016 at 03:53:53PM +0100, Marco Martin wrote:
> On Tuesday 09 February 2016 14:38:42 Sebastian Kügler wrote:
> > > Sorry, that's just broken.
> >
> > Can we make it react to horizontal swipe, but nothing else?
>
> no, for how Qt events work, once it eats the events there, the even
On Monday 08 February 2016 12:05:04 Dirk Hohndel wrote:
> On Mon, Feb 08, 2016 at 11:48:24AM -0800, Dirk Hohndel wrote:
> > I'm running into a pretty significant issues with the ActionButton:
> >
> > Its MouseArea has an implicitWidth of parent.width. Which means that my
> > page will not receive
On Monday 08 February 2016 12:05:04 Dirk Hohndel wrote:
> > The issue appears to be that onClicked ALWAYS accepts the event. Even
> > though the onClicked code simply returns if the click wasn't on the
> > button (the math for that was just recently fixed) - the ListView
> > "behind" never receives
On Tuesday 09 February 2016 14:38:42 Sebastian Kügler wrote:
> > Sorry, that's just broken.
>
> Can we make it react to horizontal swipe, but nothing else?
no, for how Qt events work, once it eats the events there, the events are
eaten and items under it will never receive anything.
I think I wo
On Tuesday, February 09, 2016 05:56:53 AM Dirk Hohndel wrote:
> On Tue, Feb 09, 2016 at 12:06:37PM +0100, Marco Martin wrote:
> > On Monday 08 February 2016 11:48:24 Dirk Hohndel wrote:
> > > I'm running into a pretty significant issues with the ActionButton:
> > >
> > >
> > > Its MouseArea has an
On Tue, Feb 09, 2016 at 12:06:37PM +0100, Marco Martin wrote:
> On Monday 08 February 2016 11:48:24 Dirk Hohndel wrote:
> > I'm running into a pretty significant issues with the ActionButton:
> >
> > Its MouseArea has an implicitWidth of parent.width. Which means that my page
> > will not receive
On Monday 08 February 2016 11:48:24 Dirk Hohndel wrote:
> I'm running into a pretty significant issues with the ActionButton:
>
> Its MouseArea has an implicitWidth of parent.width. Which means that my page
> will not receive any clicks at all in the horizontal band that includes the
> ActionButto
On Mon, Feb 08, 2016 at 11:48:24AM -0800, Dirk Hohndel wrote:
>
> I'm running into a pretty significant issues with the ActionButton:
>
> Its MouseArea has an implicitWidth of parent.width. Which means that my page
> will not receive any clicks at all in the horizontal band that includes the
>
24 matches
Mail list logo
