Hi Richard, :D
Richard Gaskin wrote:
> Your headache won't end
> until your RAM chips arrive. :)\
Thankfully, a small cup of coffee with half lemon
reduced the headache to a minimum of discomfort.
It's there, the headache is still there but in a
second or third plane... :D
> I like DIY solutions
Alejandro Tejada wrote:
> Check this script. This code would be a starting point for a script
> that implement this swiping card feature. Maybe I will try to code it
> myself when my headache ends.
Your headache won't end until your RAM chips arrive. :)\
> After we have 3 images (from previous
Hi All,
Check this script. This code would be a starting point for a script that
implement this swiping card feature. Maybe I will try to code it myself
when my headache ends.
After we have 3 images (from previous, current and next card,) the script
of top image (image of current card) just have
That's a good point. Android apps commonly uses "swipe down" to trigger a
refresh. The swipe still physically happens, but there's just a gray
background behind it, and it pops back into place and resets.
The main problem seems to be what happens during a swipe. Part of the
effect is the feedback
Matt Maier wrote:
> Maybe each card could have a parameter like "swipeTo" which would be
> the id of another card. Default could be nothing, which would disable
> swipe. But if there's a card id in there then swiping would put that
> card "underneath" so it's visible as the current card moves and
Paul Dupuis wrote:
> On 4/26/2017 3:02 PM, Richard Gaskin via use-livecode wrote:
>> Either way, the gestures themselves are only part of the challenge.
>> In fact, for card swiping we need only one, a swipe. The bigger part
>> is handling the dual-card render during the gesture.
>
>
> This would
Maybe each card could have a parameter like "swipeTo" which would be the id
of another card. Default could be nothing, which would disable swipe. But
if there's a card id in there then swiping would put that card "underneath"
so it's visible as the current card moves and if the swipe gesture
comple
On 4/26/2017 3:02 PM, Richard Gaskin via use-livecode wrote:
> Either way, the gestures themselves are only part of the challenge.
> In fact, for card swiping we need only one, a swipe. The bigger part
> is handling the dual-card render during the gesture.
This would work (in theory) for the vi
This is an important subject, I've been meaning to write this for a couple of
weeks, but Richard got here first.
our current app.
(if anyone is interested I can send you the git repo link off line…it is
public; I just don't want to post It public)
use click and swipe "everywhere"
the model i
Mike Kerner wrote:
> On Wed, Apr 26, 2017 at 2:50 PM, Richard Gaskin wrote:
>
>> Mike Kerner wrote:
>> > So you'd like a swipe event instead of using nav buttons.
>>
>> Button where appropriate, swiping where appropriate.
...
> so bug 9320?
I suppose it's related, but indirectly. That request is
so bug 9320?
On Wed, Apr 26, 2017 at 2:50 PM, Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Mike Kerner wrote:
>
> > So you'd like a swipe event instead of using nav buttons.
>
> Button where appropriate, swiping where appropriate.
>
>
> iOS:
>Use touch gestures to
Mike Kerner wrote:
> So you'd like a swipe event instead of using nav buttons.
Button where appropriate, swiping where appropriate.
iOS:
Use touch gestures to create fluidity. Make it easy to move
through your interface with minimum friction. For example,
you could let people swipe fr
So you'd like a swipe event instead of using nav buttons.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-l
I stumbled across this thread and it got me thinking:
http://forums.livecode.com/viewtopic.php?f=7&t=29184
LC has cards, which are great for many things but somewhat limited.
For example, as the OP asks about there: how does one swipe between them?
That seems a perfectly reasonable expectation,
14 matches
Mail list logo
