date:20170921


On 9/21/17 12:57 PM, Sannyasin Brahmanathaswami via use-livecode wrote:


Would be super if we could build this into the widget.. so you could, e.g set 
the width to 100 pixels height to 20 align the SVG to the left, center or right 
but the whole 100X20 region would be reactive, even if the SVG only occupied 20 
X 20.  Is that worth an enhancement request?


Yes, definitely. I think the widget only needs to allow us to set margins.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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-livecode

Re: Best way to copy from one stack to another

2017-09-21 Thread Brian Milby via use-livecode

Just thought I'd try this out and see if there is another option.  If you
right click on a card and dismiss the pop-up menu, then the edit menu
changes to "Cut Card", "Copy Card", "Clear Card", and "Duplicate Card"
although Clear and Duplicate don't seem to do anything.  Probably not much
more efficient than leaving "copy this card" in the message box, but may be.

On Thu, Sep 21, 2017 at 1:02 PM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> For some reason I've never understood, there is no menu item to copy a
> card, but it is easy to do in script or the message box:
>
>   copy this card
>
> Once that's done you can use Cmd-V to paste the card into the target
> stack. Alternately you can do:
>
>   copy card x of stack y to stack z
>
> For only a few cards, I usually find it easier to just leave "copy this
> card" in the message box, hit the return key, and manually paste into the
> target stack. After that all I have to do is navigate to the next card I
> want to copy and hit the return key again in the message box.
>
> If you have a fair number of cards to move, then a short handler with a
> repeat loop is easier, using the "copy ... to" option above.
>
>
> On 9/21/17 12:19 AM, ELS prothero via use-livecode wrote:
>
>> With all of the new versions and capabilities being added to livecode, I
>> have found need to copy parts of one stack which is older, to a new stack,
>> which is new and better. I have found it difficult to use cut and paste to
>> copy groups or other elements from one stack to another using the PB.
>>
>> Do I need to do this in code? Or is there an IDE way to copy groups and
>> other elements, including their scripts, from one card of a stack to
>> another card of  another stack?
>>
>
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.com
>
>
> ___
> 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-livecode
>
___
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-livecode

Re: Moving on from 8.* to 9.*

2017-09-21 Thread Brian Milby via use-livecode

DP9 should have the fixes from the 8 branch.  Essentially any bug fix on
the 8.1 branch will get merged into the 8.2 branch.  Any bug fixes from 8.1
or 8.2 will get merged into the 9.0 branch.  In GitHub, there have been a
bunch of these type of merges recently.  If you are up to compiling the
community edition, you can have bleeding edge all the time :)

On Thu, Sep 21, 2017 at 1:58 PM, Sannyasin Brahmanathaswami via
use-livecode  wrote:

> I'm naïve about how these branches work. Probably need a firmware update
> in my brain on this whole "future" versions thing.
>
> I had to "regress' to 8.1.7 RC1  because 8.2 DP 1 because the IDE melted
> down pretty rapidly.
>
> You wrote: " When v9 goes final v8 will no longer be maintained"
>
> Yes, of course… that's a given. But as of today: Isn't v9  missing *all*
> the patches to the product since March of this year? Wouldn't HQ need to
> merge everything thru 8.1.7 into 9? and if that was already done, wouldn't
> it's date in the download section reflect the date that happened?
>
> Otherwise, if we use 9 aren't we facing things already solved in the 8.1.*
> branch between March and September of this year?
>
> What am I missing?
>
> BR
>
> Richard Gaskin wrote:
>
> > 1) using 9. that old doesn’t' work for us.. We have got too much
> > vested in  8.* that works well, can't risk it.
>
> When v9 goes final v8 will no longer be maintained.  Given the changes
> we can expect in OSes, esp. mobile, not keeping current will eventually
> shut down your project.
>
> What are the bug report numbers for the issues you've encountered with
> v9?  Let's see if we can resolve those so your project can keep current
> with OS changes as smoothly as possible.
>
>
>
> ___
> 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-livecode
>
___
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-livecode

Re: Constraining an input field's contents to be a single line.

2017-09-21 Thread Alex Tweedly via use-livecode

On 21/09/2017 16:14, Richard Gaskin via use-livecode wrote:

Alex Tweedly wrote:
> I do not currently have "mobile text field objects" - all I have
> are just standard LC fields, so returninfield is all I need for
> the 'return' part of the problem - no need for 'inputReturnKey'.

If this is just for yourself then the following may not matter much, 
since you know what to expect and can handle whatever you choose to make.

But if this app is for others to use, using a LiveCode-native field 
instead of a mobile-native field will very quickly show why 
mobile-native fields are important.

That's exactly what I've been missing - I've been fretting about one or 
two details of LC-fields on mobile, not realizing that there are 
overwhelming limitations that mean I should just forget about LC-native 
fields if mobile is a primary target.

So now I need to go off and figure out the most appropriate way (for the 
short term) to handle having different controls for different platforms.

So I've learnt a lot - but taken rather longer than I should have to 
realize I was counting angels on the wrong pinheads :-)

Thanks to everyone for all the suggestions that helped to get me here.

Alex.

___
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-livecode

Re: Best way to copy from one stack to another

The other way to force the card to be selected is to double click somewhere 
where there are no visible objects. This will open the Card Inspector at which 
point the menus will work accordingly. 

Bob S


> On Sep 21, 2017, at 16:12 , Bob Sneidar via use-livecode 
>  wrote:
> 
> Ill be dammed. Gobsmacked. It appears that the menu *ought* to change 
> contextually when you click on a card, but doesn't. Right clicking on the 
> card seems to force the IDE to focus on the card itself. Neat trick. It also 
> reveals that the IDE was written and intended to allow 
> cut/copy/paste/duplicate cards, but somehow the ability to "click" on a card 
> is what is missing. 
> 
> Bob S
> 
> 
>> On Sep 21, 2017, at 15:51 , Brian Milby via use-livecode 
>>  wrote:
>> 
>> Just thought I'd try this out and see if there is another option.  If you
>> right click on a card and dismiss the pop-up menu, then the edit menu
>> changes to "Cut Card", "Copy Card", "Clear Card", and "Duplicate Card"
>> although Clear and Duplicate don't seem to do anything.  Probably not much
>> more efficient than leaving "copy this card" in the message box, but may be.
> 
> 
> ___
> 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-livecode


___
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-livecode

Re: Best way to copy from one stack to another

Ill be dammed. Gobsmacked. It appears that the menu *ought* to change 
contextually when you click on a card, but doesn't. Right clicking on the card 
seems to force the IDE to focus on the card itself. Neat trick. It also reveals 
that the IDE was written and intended to allow cut/copy/paste/duplicate cards, 
but somehow the ability to "click" on a card is what is missing. 

Bob S

> On Sep 21, 2017, at 15:51 , Brian Milby via use-livecode 
>  wrote:
> 
> Just thought I'd try this out and see if there is another option.  If you
> right click on a card and dismiss the pop-up menu, then the edit menu
> changes to "Cut Card", "Copy Card", "Clear Card", and "Duplicate Card"
> although Clear and Duplicate don't seem to do anything.  Probably not much
> more efficient than leaving "copy this card" in the message box, but may be.

___
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-livecode

Re: Scrolling Groups on Mobile - Show a little of what is below

2017-09-21 Thread Jim Lambert via use-livecode

Some mobile UI’s, when first showing a scrolling list that extends below the 
visible area, will slightly “bounce” the list contents up then back down.  This 
does double duty. It briefly reveals the hidden content and indicates that the 
list is scrollable. And it works regardless of screen height.

Jim Lambert
___
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-livecode

Re: Constraining an input field's contents to be a single line.

2017-09-21 Thread Roger Eller via use-livecode

Have you tried...?

*on* rawKeyDown
   *if* pKeyPressed is 65293 *then*
  replace cr with empty in me
  select after me
   *end if*
   pass rawKeyDown
*end* rawKeyDown


On Wed, Sep 20, 2017 at 5:40 PM, Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Thanks for the prompt Mike.
>
> Short answer - don't know yet, though I suspect I'm going to have to find
> out.
>
> I do not currently have "mobile text field objects" - all I have are just
> standard LC fields, so returninfield is all I need for the 'return' part of
> the problem - no need for 'inputReturnKey'.
>
> However, I also want to trap any attempt to paste in text containing CRs;
> I can do that for traditional platforms with a 'pasteKey' handler - but
> that doesn't seem to apply to LC fields on mobile, and also there doesn't
> appear to be any direct equivalent for mobile text fields (though there may
> be other ways to achieve the same result on mobile text fields - I really
> haven't looked at them yet).
>
> In fact, maybe that's the question I *should* ask.
> "Should i be  (can I reasonably get away with) using LC fields in an
> app targeted for mobiles, or do I really need to use mobile text fields ?
>
> Thanks
> Alex.
>
> On 20/09/2017 17:01, Mike Kerner via use-livecode wrote:
>
>> did that work, alex?
>>
>> On Mon, Sep 18, 2017 at 4:41 PM, Mike Kerner 
>> wrote:
>>
>> If you have a mobile text field object, then have you looked at
>>> inputReturnKey?
>>>
>>>
>>> On Mon, Sep 18, 2017 at 4:17 PM, Alex Tweedly via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>>
>>> I'm sure there must be an easy way I'm missing . he said in hope :-)

 I want a field to contain a single line of data - i.. no CRs.

 I've done the easy bit (a handler for returninfield).

 I can even do the moderate bit -  a 'pastekey' handler, and check for
 CRs
 in the clipboard - but that doesn't apply to mobile (or at least, the
 dict
 says it doesn't).

 Is there any way to handle it on mobile ?

 Thanks
 Alex.

 ___
 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-livecode

>>>
>>>
>>>
>>> --
>>> On the first day, God created the heavens and the Earth
>>> On the second day, God created the oceans.
>>> On the third day, God put the animals on hold for a few hours,
>>> and did a little diving.
>>> And God said, "This is good."
>>>
>>>
>>
>>
>
> ___
> 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-livecode
___
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-livecode

Re: Constraining an input field's contents to be a single line.

2017-09-21 Thread Roger Eller via use-livecode

The text WAS formatted and colorized.  Apparently the listserv modified
it.  The words enclosed in asterisks WERE in bold.

~Roger


On Thu, Sep 21, 2017 at 8:59 AM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:

> what do the asterisks do?
>
> On Thu, Sep 21, 2017 at 6:58 AM, Roger Eller via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Have you tried...?
> >
> > *on* rawKeyDown
> >*if* pKeyPressed is 65293 *then*
> >   replace cr with empty in me
> >   select after me
> >*end if*
> >pass rawKeyDown
> > *end* rawKeyDown
> >
> >
> > On Wed, Sep 20, 2017 at 5:40 PM, Alex Tweedly via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> > > Thanks for the prompt Mike.
> > >
> > > Short answer - don't know yet, though I suspect I'm going to have to
> find
> > > out.
> > >
> > > I do not currently have "mobile text field objects" - all I have are
> just
> > > standard LC fields, so returninfield is all I need for the 'return'
> part
> > of
> > > the problem - no need for 'inputReturnKey'.
> > >
> > > However, I also want to trap any attempt to paste in text containing
> CRs;
> > > I can do that for traditional platforms with a 'pasteKey' handler - but
> > > that doesn't seem to apply to LC fields on mobile, and also there
> doesn't
> > > appear to be any direct equivalent for mobile text fields (though there
> > may
> > > be other ways to achieve the same result on mobile text fields - I
> really
> > > haven't looked at them yet).
> > >
> > > In fact, maybe that's the question I *should* ask.
> > > "Should i be  (can I reasonably get away with) using LC fields in
> an
> > > app targeted for mobiles, or do I really need to use mobile text
> fields ?
> > >
> > > Thanks
> > > Alex.
> > >
> > > On 20/09/2017 17:01, Mike Kerner via use-livecode wrote:
> > >
> > >> did that work, alex?
> > >>
> > >> On Mon, Sep 18, 2017 at 4:41 PM, Mike Kerner <
> mikeker...@roadrunner.com
> > >
> > >> wrote:
> > >>
> > >> If you have a mobile text field object, then have you looked at
> > >>> inputReturnKey?
> > >>>
> > >>>
> > >>> On Mon, Sep 18, 2017 at 4:17 PM, Alex Tweedly via use-livecode <
> > >>> use-livecode@lists.runrev.com> wrote:
> > >>>
> > >>> I'm sure there must be an easy way I'm missing . he said in hope
> > :-)
> > 
> >  I want a field to contain a single line of data - i.. no CRs.
> > 
> >  I've done the easy bit (a handler for returninfield).
> > 
> >  I can even do the moderate bit -  a 'pastekey' handler, and check
> for
> >  CRs
> >  in the clipboard - but that doesn't apply to mobile (or at least,
> the
> >  dict
> >  says it doesn't).
> > 
> >  Is there any way to handle it on mobile ?
> > 
> >  Thanks
> >  Alex.
> > 
> >  ___
> >  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-livecode
> > 
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> On the first day, God created the heavens and the Earth
> > >>> On the second day, God created the oceans.
> > >>> On the third day, God put the animals on hold for a few hours,
> > >>> and did a little diving.
> > >>> And God said, "This is good."
> > >>>
> > >>>
> > >>
> > >>
> > >
> > > ___
> > > 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-livecode
> > ___
> > 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-livecode
> >
>
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>and did a little diving.
> And God said, "This is good."
> ___
> 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-livecode
>
___
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-livecode

Re: Best way to copy from one stack to another

2017-09-21 Thread Randy Hengst via use-livecode

Take a look at “copy” in the dictionary… I’ve used this script in a button on a 
card I wanted to move:

on mouseUp

copy this card to stack “targetStack"

end mouseUp



> On Sep 21, 2017, at 12:19 AM, ELS prothero via use-livecode 
>  wrote:
> 
> Folks:
> With all of the new versions and capabilities being added to livecode, I have 
> found need to copy parts of one stack which is older, to a new stack, which 
> is new and better. I have found it difficult to use cut and paste to copy 
> groups or other elements from one stack to another using the PB. 
> 
> Do I need to do this in code? Or is there an IDE way to copy groups and other 
> elements, including their scripts, from one card of a stack to another card 
> of  another stack?
> Tnx,
> Bill
> 
> William Prothero, PhD
> Professor Emeritus
> University of California, Santa Barbara
> http://earthlearningsolutions.org
> 
> ___
> 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-livecode

___
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-livecode

Re: Constraining an input field's contents to be a single line.

what do the asterisks do?

On Thu, Sep 21, 2017 at 6:58 AM, Roger Eller via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Have you tried...?
>
> *on* rawKeyDown
>*if* pKeyPressed is 65293 *then*
>   replace cr with empty in me
>   select after me
>*end if*
>pass rawKeyDown
> *end* rawKeyDown
>
>
> On Wed, Sep 20, 2017 at 5:40 PM, Alex Tweedly via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Thanks for the prompt Mike.
> >
> > Short answer - don't know yet, though I suspect I'm going to have to find
> > out.
> >
> > I do not currently have "mobile text field objects" - all I have are just
> > standard LC fields, so returninfield is all I need for the 'return' part
> of
> > the problem - no need for 'inputReturnKey'.
> >
> > However, I also want to trap any attempt to paste in text containing CRs;
> > I can do that for traditional platforms with a 'pasteKey' handler - but
> > that doesn't seem to apply to LC fields on mobile, and also there doesn't
> > appear to be any direct equivalent for mobile text fields (though there
> may
> > be other ways to achieve the same result on mobile text fields - I really
> > haven't looked at them yet).
> >
> > In fact, maybe that's the question I *should* ask.
> > "Should i be  (can I reasonably get away with) using LC fields in an
> > app targeted for mobiles, or do I really need to use mobile text fields ?
> >
> > Thanks
> > Alex.
> >
> > On 20/09/2017 17:01, Mike Kerner via use-livecode wrote:
> >
> >> did that work, alex?
> >>
> >> On Mon, Sep 18, 2017 at 4:41 PM, Mike Kerner  >
> >> wrote:
> >>
> >> If you have a mobile text field object, then have you looked at
> >>> inputReturnKey?
> >>>
> >>>
> >>> On Mon, Sep 18, 2017 at 4:17 PM, Alex Tweedly via use-livecode <
> >>> use-livecode@lists.runrev.com> wrote:
> >>>
> >>> I'm sure there must be an easy way I'm missing . he said in hope
> :-)
> 
>  I want a field to contain a single line of data - i.. no CRs.
> 
>  I've done the easy bit (a handler for returninfield).
> 
>  I can even do the moderate bit -  a 'pastekey' handler, and check for
>  CRs
>  in the clipboard - but that doesn't apply to mobile (or at least, the
>  dict
>  says it doesn't).
> 
>  Is there any way to handle it on mobile ?
> 
>  Thanks
>  Alex.
> 
>  ___
>  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-livecode
> 
> >>>
> >>>
> >>>
> >>> --
> >>> On the first day, God created the heavens and the Earth
> >>> On the second day, God created the oceans.
> >>> On the third day, God put the animals on hold for a few hours,
> >>> and did a little diving.
> >>> And God said, "This is good."
> >>>
> >>>
> >>
> >>
> >
> > ___
> > 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-livecode
> ___
> 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-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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-livecode

Re: How to to type bottom to up and right to left in a field

Whut? All that will do is replace spaces with spaces. That will not reverse the 
order of the typed text. 

Bob S


> On Sep 21, 2017, at 03:00 , hh via use-livecode 
>  wrote:
> 
> on textChanged
>  replace space with space in me -- or whatever
> end textChanged


___
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-livecode

Re: Best way to copy from one stack to another

2017-09-21 Thread Dr. Hawkins via use-livecode

On Thu, Sep 21, 2017 at 4:05 AM, Randy Hengst via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
>
> copy this card to stack “targetStack"


Or even make the old stack (or a copy of oil) a sub stack of the new stack.
-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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-livecode

Re: Scrolling Groups on Mobile - Show a little of what is below

That used to be a scroll bar. Of course mobile devices do not have those, they 
have wheels. Perhaps using a scrolling wheel is a better choice for lists. 

Bob S


> On Sep 21, 2017, at 08:14 , Mike Kerner via use-livecode 
>  wrote:
> 
> I agree with J.  The simplest visual cue that there is something in the box
> is for the lid to be ajar.  Cabinets with the door ajar begged to be open.
> Doors that are mostly but not completely closed are the same way.  Lists
> should carry the same cue.


___
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-livecode

Re: Constraining an input field's contents to be a single line.

Alex Tweedly wrote:
> I do not currently have "mobile text field objects" - all I have
> are just standard LC fields, so returninfield is all I need for
> the 'return' part of the problem - no need for 'inputReturnKey'.

If this is just for yourself then the following may not matter much, 
since you know what to expect and can handle whatever you choose to make.

But if this app is for others to use, using a LiveCode-native field 
instead of a mobile-native field will very quickly show why 
mobile-native fields are important.

Ideally of course, given the central role editable text plays in apps, 
there would be just one object that can work in the IDE and on the device.

And fortunately that was funded a while back:

Infinite LiveCode: Native Field Object
https://livecode.com/project/infinite-livecode-native-field-object/

IIRC that completion is dependent on the completion of some other 
aspects of LCB which are still being refined, so in the meantime we need 
to work with what we have, weighing the tradeoffs between LC-native 
fields and mobile-native.

The biggest is how selection is handled.  LC-native fields will bring up 
the device keyboard when entered, and you can type into them.  But 
that's petty much it.  Designed as they were for the desktop, selection 
is fundamentally different.

The mobile-native text editing experience users are accustomed to allows 
them to drag-select text, or long-press to select a word, and once a 
selection has been made handle controls appear at each end of the 
selection run, which can be dragged to adjust the selection.

There's also a popup panel that the OS provides when a text selection is 
active in a mobile-native field, offering a menu of options for common 
commands like Cut, Copy, Paste, Select All, and sometimes Search and others.

When attempting to emulate mobile-native fields using LC-native fields, 
you'll have to make all of those UI elements from scratch.  And since 
clipboard control is not currently supported by LC on mobile as it is on 
the desktop, any sort of copy and paste that would work between apps as 
users expect would be difficult if not impossible to achieve.

But when using a mobile-native field, you get all that for free.

For a brief while I once considered trying to come up with a framework 
for emulating mobile-native fields with LC-native fields.  It was 
daunting enough to deal with the tedium of crafting the selection 
handles, and the absence of integrated clipboard support ultimately 
prompted me to stop and put my time into more productive tasks.

You're a very talented and nimble thinker, but I suspect you'll find 
that until we get one field control that works in both the IDE and on 
mobile devices, you'll have a much better time focusing on ways to use 
mobile-native fields.

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web

 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
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-livecode

Re: Scrolling Groups on Mobile - Show a little of what is below

It has to be visible, which is a problem on ios, at least.

On Thu, Sep 21, 2017 at 11:20 AM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:

> That used to be a scroll bar. Of course mobile devices do not have those,
> they have wheels. Perhaps using a scrolling wheel is a better choice for
> lists.
>
> Bob S
>
>
> > On Sep 21, 2017, at 08:14 , Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > I agree with J.  The simplest visual cue that there is something in the
> box
> > is for the lid to be ajar.  Cabinets with the door ajar begged to be
> open.
> > Doors that are mostly but not completely closed are the same way.  Lists
> > should carry the same cue.
>
>
> ___
> 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-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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-livecode

Re: Scrolling Groups on Mobile - Show a little of what is below

and even the presence of a scrollbar on a desktop interface doesn't really
jump up and say "THERE'S MORE!" because it can be disabled due to there not
being anything more.  The difference can be subtle.

On Thu, Sep 21, 2017 at 11:26 AM, Mike Kerner 
wrote:

> It has to be visible, which is a problem on ios, at least.
>
> On Thu, Sep 21, 2017 at 11:20 AM, Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> That used to be a scroll bar. Of course mobile devices do not have those,
>> they have wheels. Perhaps using a scrolling wheel is a better choice for
>> lists.
>>
>> Bob S
>>
>>
>> > On Sep 21, 2017, at 08:14 , Mike Kerner via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> >
>> > I agree with J.  The simplest visual cue that there is something in the
>> box
>> > is for the lid to be ajar.  Cabinets with the door ajar begged to be
>> open.
>> > Doors that are mostly but not completely closed are the same way.  Lists
>> > should carry the same cue.
>>
>>
>> ___
>> 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-livecode
>>
>
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>and did a little diving.
> And God said, "This is good."
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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-livecode

Re: How to to type bottom to up and right to left in a field

> > hh wrote:
> > on textChanged
> >  replace space with space in me -- or whatever
> > end textChanged
> Bob S. wrote:
> Whut? All that will do is replace spaces with spaces. That will not reverse 
> the order of the typed text. 

(Instead of "space" use also any other char, for example "cr")
It works. Just try. 



___
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-livecode

Re: Moving on from 8.* to 9.*

Sannyasin Brahmanathaswami wrote:

> 1) using 9. that old doesn’t' work for us.. We have got too much
> vested in  8.* that works well, can't risk it.

When v9 goes final v8 will no longer be maintained.  Given the changes 
we can expect in OSes, esp. mobile, not keeping current will eventually 
shut down your project.

What are the bug report numbers for the issues you've encountered with 
v9?  Let's see if we can resolve those so your project can keep current 
with OS changes as smoothly as possible.

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web

 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
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-livecode

Re: Scrolling Groups on Mobile - Show a little of what is below

I agree with J.  The simplest visual cue that there is something in the box
is for the lid to be ajar.  Cabinets with the door ajar begged to be open.
Doors that are mostly but not completely closed are the same way.  Lists
should carry the same cue.

On Thu, Sep 21, 2017 at 1:45 AM, Alan via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi BR
>
> What's lacking is the visual feedback that there's something "more"...
>
> One way you might give an indication could be to flash the mobile
> scrollbars to show how much of the group is visible.
>
> e.g.
> smControlSet sScrollerID, "indicatorStyle", "white"
> smControlSet sScrollerID, "vIndicator", true
>
> I can't remember now if the indicator flashes by itself or not, but if not
> then just send messages in time to show then hide then show again to
> "flash" it...
>
> Maybe that'd work?
>
> HTH
>
> cheers
>
> Alan
>
> > On 21 Sep 2017, at 2:50 pm, Sannyasin Brahmanathaswami 
> wrote:
> >
> >
> > FYI this is a tip that came from Jacque, but I had to experience it
> "live" myself. Alex though it useful to share?
> >
> > On a busy day here (we have 100 plus visitors daily) I will go outside
> and get complete strangers to  download the new app and watch them as they
> go thru initial install and usage.
> >
> > Fascinating to watch e.g. our pixel perfect fit of rows on the home
> screen is for a scrolling group that has more rows below screen.. But this
> is "wrong" because the proper way to do it is, says Jacque: create the rows
> so the bottom one is a bit cut off, otherwise a subset of users never try
> to scroll up!
> >
> > Yep.. I had several users tap on the content to go to the links that
> appeared there. they would go "home" and tap the next one.. and never swipe
> up?
> >
> > They think what they see it all there is.  But when you show half of a
> row at the bottom, the user instinctively swipes up?? But the screens were
> designed by a graphic designer who does magazine design? not app design? so
> his design instinct is for the printed page and he will always strive for a
> "perfect fit"  and all trouble we went to take 736 pixes height, subtract
> the hero image on top and divide the remainder *exactly* so that row would
> fit precisely.. only shot our UX in the foot? ha!
> >
> > from the land of
> >
> > Things you will never know
> > unless you watch over someone's shoulder
> > while they try to use your software.
> >
> > BR
>
>
> ___
> 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-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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-livecode

Re: Constraining an input field's contents to be a single line.

Me too. :-)

Bob S


> On Sep 21, 2017, at 08:11 , Mike Kerner via use-livecode 
>  wrote:
> 
> Yes, I was trying to be funny, but it didn't work like I was hoping...


___
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-livecode

Re: Constraining an input field's contents to be a single line.

confuse people. It's a function of copying from his email app. 

Bob S


> On Sep 21, 2017, at 05:59 , Mike Kerner via use-livecode 
>  wrote:
> 
> what do the asterisks do?


___
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-livecode

Re: Best way to copy from one stack to another

2017-09-21 Thread William Prothero via use-livecode

Thanks, Richard. I guess I could do that for specific elements on a card too. 
Pretty simple. I had expected I could just cut and paste from the project 
browser. Just coding it is easy too.
Bill P

William A. Prothero
http://earthlearningsolution.org/

> On Sep 21, 2017, at 7:57 AM, Dr. Hawkins via use-livecode 
>  wrote:
> 
> On Thu, Sep 21, 2017 at 4:05 AM, Randy Hengst via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>> 
>> 
>> copy this card to stack “targetStack"
> 
> 
> Or even make the old stack (or a copy of oil) a sub stack of the new stack.
> -- 
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> ___
> 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-livecode

___
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-livecode

Re: Constraining an input field's contents to be a single line.

Yes, I was trying to be funny, but it didn't work like I was hoping...

On Thu, Sep 21, 2017 at 10:43 AM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:

> confuse people. It's a function of copying from his email app.
>
> Bob S
>
>
> > On Sep 21, 2017, at 05:59 , Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > what do the asterisks do?
>
>
> ___
> 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-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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-livecode

Re: How to to type bottom to up and right to left in a field

2017-09-21 Thread dunbarx via use-livecode

Hi.

Not sure at all what that handler does. But something like this, off the top
of my head:

on keyDown, tKey
   if the optionKey is down then put return & tKey before me
   else put tKey before me
end keyDown

Craig Newman



--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
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-livecode

Re: Constraining an input field's contents to be a single line.

2017-09-21 Thread AndyP via use-livecode

Easiest way... add this to the field

on returninField
   exit returninField
end returninField





-
Andy Piddock 


My software never has bugs. It just develops random features. 

TinyIDE a Free alternative minimalist IDE Plugin for LiveCode
TinyIDE 


Script editor Themer for LC http://2108.co.uk  

PointandSee is a FREE simple but full featured under cursor colour picker / 
finder.
http://www.pointandsee.co.uk  - made with LiveCode
--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
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-livecode

Re: Constraining an input field's contents to be a single line.

2017-09-21 Thread AndyP via use-livecode

Add this to the field script

on returninField
   exit returninField
end returninField



-
Andy Piddock 


My software never has bugs. It just develops random features. 

TinyIDE a Free alternative minimalist IDE Plugin for LiveCode
TinyIDE 


Script editor Themer for LC http://2108.co.uk  

PointandSee is a FREE simple but full featured under cursor colour picker / 
finder.
http://www.pointandsee.co.uk  - made with LiveCode
--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
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-livecode

Re: How to to type bottom to up and right to left in a field

2017-09-21 Thread Sannyasin Brahmanathaswami via use-livecode

hh wrote:

> hh wrote:
> on textChanged
> replace space with space in me -- or whatever
> end textChanged
Bob S. wrote:
Whut? All that will do is replace spaces with spaces. That will not reverse the order of the typed text.

(Instead of "space" use also any other char, for example "cr")
It works. Just try.

Indeed it does. At first glance the behavior seems at least
unintuitive. It also appears to prevent the Backspace key from having
any effect. Is it a bug? A feature?

Hmmm...

On further consideration it may make sense, since the selection is
removed by replacing the field contents, and the default selection is at
the beginning of a line.

It would seem the only way to preserve the insertion point would be to
separately trap for all relevant messages (backspaceKey, pasteKey,
dragDrop, keyDown, etc.), where you first query the selectedChunk,
perform the action, then adjust the selectedChunk according to the
length of the operation, and then restore the insertion point at the
adjusted offset.

This seems like so many things in a good scripting language: when you
want to do something ordinary, the provided behaviors make the task
uncommonly easy. But when you want to do something extraordinary, the
task is uncommonly difficult.

--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web

ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
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-livecode

Re: Moving on from 8.* to 9.*

I'm naïve about how these branches work. Probably need a firmware update in my 
brain on this whole "future" versions thing.

I had to "regress' to 8.1.7 RC1  because 8.2 DP 1 because the IDE melted down 
pretty rapidly.

You wrote: " When v9 goes final v8 will no longer be maintained"  

Yes, of course… that's a given. But as of today: Isn't v9  missing *all* the 
patches to the product since March of this year? Wouldn't HQ need to merge 
everything thru 8.1.7 into 9? and if that was already done, wouldn't it's date 
in the download section reflect the date that happened?

Otherwise, if we use 9 aren't we facing things already solved in the 8.1.* 
branch between March and September of this year?

What am I missing?

BR

Richard Gaskin wrote:

> 1) using 9. that old doesn’t' work for us.. We have got too much
> vested in  8.* that works well, can't risk it.

When v9 goes final v8 will no longer be maintained.  Given the changes 
we can expect in OSes, esp. mobile, not keeping current will eventually 
shut down your project.

What are the bug report numbers for the issues you've encountered with 
v9?  Let's see if we can resolve those so your project can keep current 
with OS changes as smoothly as possible.

___
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-livecode

Re: SivaSiva iOS App Approved - Android Issues/AcceleratedRendering issues

2017-09-21 Thread Sannyasin Brahmanathaswami via use-livecode

Jonathan

Right -- Excellent. Thanks. I missed that before.. and yes I had this same 
experience and asked myself "What happened?"

OK I'll have to go back and look that up, well work doing. Agreed. I guess was 
testing so much in Android, I forgot that apple actually closes.  Would be nice 
to expose this in the LC SA settings for iOS.



On 9/19/17, 9:01 AM, "use-livecode on behalf of Jonathan Lynch via 
use-livecode"  wrote:

I was in the app and went to the section where it profiled your community 
members with a browser widget, pulled from your website, I think. When I got 
out and got back in, I had to navigate to the same place. With Ralph's plist 
hack, on iOS, it will sleep rather than close. That way, when you get back into 
it, the app is in the same place as when you left.

I was just giving you my initial observations.



___
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-livecode

Re: Constraining an input field's contents to be a single line.

2017-09-21 Thread Sannyasin Brahmanathaswami via use-livecode

well, if you have tmc2, then native mobile fields are a breeze.  If you
don't, then they're still pretty easy once you make your first one.

On Thu, Sep 21, 2017 at 7:32 PM, Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 21/09/2017 16:14, Richard Gaskin via use-livecode wrote:
>
> Alex Tweedly wrote:
>> > I do not currently have "mobile text field objects" - all I have
>> > are just standard LC fields, so returninfield is all I need for
>> > the 'return' part of the problem - no need for 'inputReturnKey'.
>>
>> If this is just for yourself then the following may not matter much,
>> since you know what to expect and can handle whatever you choose to make.
>>
>> But if this app is for others to use, using a LiveCode-native field
>> instead of a mobile-native field will very quickly show why mobile-native
>> fields are important.
>>
>> That's exactly what I've been missing - I've been fretting about one or
> two details of LC-fields on mobile, not realizing that there are
> overwhelming limitations that mean I should just forget about LC-native
> fields if mobile is a primary target.
>
> So now I need to go off and figure out the most appropriate way (for the
> short term) to handle having different controls for different platforms.
>
> So I've learnt a lot - but taken rather longer than I should have to
> realize I was counting angels on the wrong pinheads :-)
>
> Thanks to everyone for all the suggestions that helped to get me here.
>
> Alex.
>
>
> ___
> 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-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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-livecode

Re: Scrolling Groups on Mobile - Show a little of what is below

done

http://quality.livecode.com/show_bug.cgi?id=20445

please add as you think useful.

 
On 9/21/17, 11:51 AM, "use-livecode on behalf of J. Landman Gay via 
use-livecode"  wrote:

>Would be super if we could build this into the widget.. so you could, e.g 
set the width to 100 pixels height to 20 align the SVG to the left, center or 
right but the whole 100X20 region would be reactive, even if the SVG only 
occupied 20 X 20.  Is that worth an enhancement request?

Yes, definitely. I think the widget only needs to allow us to set margins.

___
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-livecode

Re: Best way to copy from one stack to another

2017-09-21 Thread Sannyasin Brahmanathaswami via use-livecode


I'm astounded too. I wonder how long that's been there.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com



On September 21, 2017 6:14:49 PM Bob Sneidar via use-livecode 
 wrote:


Ill be dammed. Gobsmacked. It appears that the menu *ought* to change 
contextually when you click on a card, but doesn't. Right clicking on the 
card seems to force the IDE to focus on the card itself. Neat trick. It 
also reveals that the IDE was written and intended to allow 
cut/copy/paste/duplicate cards, but somehow the ability to "click" on a 
card is what is missing.


Bob S


On Sep 21, 2017, at 15:51 , Brian Milby via use-livecode 
 wrote:


Just thought I'd try this out and see if there is another option.  If you
right click on a card and dismiss the pop-up menu, then the edit menu
changes to "Cut Card", "Copy Card", "Clear Card", and "Duplicate Card"
although Clear and Duplicate don't seem to do anything.  Probably not much
more efficient than leaving "copy this card" in the message box, but may be.



___
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-livecode




___
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-livecode

Re: Scrolling Groups on Mobile - Show a little of what is below

I've seen that also, though it looks cool initially, I'm not sure a regular 
user of the app would want to have that "noise" every time they go to that 
screen it it were a "home" screen. But it's  a good option for some use cases, 
for sure.

But following on Jacque's essay on user testing and "ruthless refactoring based 
on feedback"  and another thing I saw on Quora about how one attribute of 
genius is the humility and courage to throw away even a mountain of previous 
work if you can make the end result better… 

I may just try to get stackholders to let us put links to all 8 regions on the 
visible region and scrap the scroller. Our new designer in Croatia created that 
exact screen for me (without my asking her to) in Invision...  and younger 
users who I have given a "no holds bar feedback license" are pretty vocal about 
it… "It's only 8 links… why do you make us scroll?" Older users like it though… 
"I love the pretty little photos."  There one in each row. Many usesr don’t' 
seem to care, they are focus on content and swiping up is just natural…

UX … so many options and opinions.

Jim Lambert wrote:

Some mobile UI’s, when first showing a scrolling list that extends below 
the visible area, will slightly “bounce” the list contents up then back down.  
This does double duty. It briefly reveals the hidden content and indicates that 
the list is scrollable. And it works regardless of screen height.


___
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-livecode

Re: How to to type bottom to up and right to left in a field

2017-09-21 Thread Sannyasin Brahmanathaswami via use-livecode


Mark Waddingham wrote:

> Whenever a range of text is set in a field, the selection is set to
> the beginning of the chunk that was set - so in the case of 'replace'
> acting on the whole field, that would be the beginning.
>
> Using the '(replacing | preserving) styles' form works slightly
> differently - it iterates through the content of the field, and only
> mutates the parts which are to be replaced. So with that form, the
> selection index would end up being the beginning of the last
> occurrence of x which was replaced with y.
>
> The rule is relatively sensible I think - since if a range of text is
> replaced, the only index you can guarantee will be in the same place
> as  it was before is the beginning of the range which was replaced...

Yes, quite sensible with that description.  Thanks.

> The textChanged message is a bit of a blunt instrument -  mainly
> because it was the best we could add to the field at the time
> without potentially ending up down a whole set of rabbit warrens, or
> impacting performance too much.

As I was writing my post I pondered what a proposed change might be, and 
I couldn't think of a good one.  Yes, it is a blunt instrument, but with 
that it's also predictable, and consistent with other text messages.


Maybe there's a better way, but frankly where I've used it in real-world 
projects I've found the textChanged message very useful as-is.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
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-livecode

Re: Scrolling Groups on Mobile - Show a little of what is below

Yes… that's my plan… all I have to do is shrink the rows by 15 pixels 
vertically and the 4th one will pull up at the bottom of the screen. A bit 
tedious, but can do this with some toolbox scripts… so , not too hard.  
Actually now that I have 24 objects = 3 each for 8 rows (each one has a bkgrnd 
grc, text label and small photo, kinda like the news articles toc style) 
instead of   8 groups with 3 child objects each… it's simpler to deal with… 
only thing being you can't code against a subgroup.

I'm trying to fix as much of the "bloopers" as I can because we are doing zero 
promotion until the android bug is fixed, just confirmed yesterday by HQ… 
Accelerated rendering, again, is a problem on Android. 

So, though the initial app was accepted on iOS I'm treating it like a "beta 
test" 

We also made some other bad decisions about navigation, leaving users with 
"where am I?" in some contexts.. which are easily fixed… which also leads to:

those  SVG icon widgets do not respond to touch unless the finger is exactly on 
the visible pixels…a big "house" or "journal" icon works.. but slim forward 
back arrows… not so much… users think the app is unresponsive, but it's just 
their finger didn’t "hit it exactly" so they keep punching at the icon  (like a 
right arrow, or back arrow) until they do… nuisance.

So where we use them for navigation I have to create a small group with a 
background graphic with a blend level of 99 or so and put the script into the 
group.  I guess this would be expected since the non-drawn areas of a SVG rect 
are be default transparent but we I see this everywhere: Spotify uses some 
really small icons, but I deliberately tapped just to the side of them and they 
still fire… so I guess the SOP is to increase the response region rect for any 
navigation where you don't need that area to do anything else… may as well give 
the user a lot of touch responsive area… Would be super if we could build this 
into the widget.. so you could, e.g set the width to 100 pixels height to 20 
align the SVG to the left, center or right but the whole 100X20 region would be 
reactive, even if the SVG only occupied 20 X 20.  Is that worth an enhancement 
request?

BR

Kerner wrote:

I agree with J.  The simplest visual cue that there is something in the box
is for the lid to be ajar.  Cabinets with the door ajar begged to be open.
Doors that are mostly but not completely closed are the same way.  Lists
should carry the same cue.

___
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-livecode

Re: Best way to copy from one stack to another

For some reason I've never understood, there is no menu item to copy a 
card, but it is easy to do in script or the message box:


  copy this card

Once that's done you can use Cmd-V to paste the card into the target 
stack. Alternately you can do:


  copy card x of stack y to stack z

For only a few cards, I usually find it easier to just leave "copy this 
card" in the message box, hit the return key, and manually paste into 
the target stack. After that all I have to do is navigate to the next 
card I want to copy and hit the return key again in the message box.


If you have a fair number of cards to move, then a short handler with a 
repeat loop is easier, using the "copy ... to" option above.



On 9/21/17 12:19 AM, ELS prothero via use-livecode wrote:

With all of the new versions and capabilities being added to livecode, I have 
found need to copy parts of one stack which is older, to a new stack, which is 
new and better. I have found it difficult to use cut and paste to copy groups 
or other elements from one stack to another using the PB.

Do I need to do this in code? Or is there an IDE way to copy groups and other 
elements, including their scripts, from one card of a stack to another card of  
another stack?



--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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-livecode

Re: How to to type bottom to up and right to left in a field

2017-09-21 Thread Mark Waddingham via use-livecode


On 2017-09-21 19:48, Mark Waddingham via use-livecode wrote:



For example, let's say you have a right to left language FOO which has
letters A, B, C; compared to a left to right language BAR which has
letters X, Y and Z. Hello in FOO is spoken A-B-C; Hello in BAR is
spoken X-Y-Z. However, as FOO is right to left, Hello is written CBA.
If these languages were mixed in a single piece of text - spoken as
A-B-C X-Y-Z - then in memory the order would be ABC XYZ, but visually
it would appear as either:

  i) from the left edge - CBA XYZ

  ii) from the right edge - XYZ CBA

Whether it would be (i) or (ii) depends on which is considered to be
the dominant language in that case and context.




I should perhaps have mentioned the 'useful' outcome of the above 
tangent...


If text is always stored in memory in logical order (in the order we 
utter it / actually read the individual constituent parts), then 
processing of a string containing left-to-right text, or right-to-left 
text or any mixed combination there-of needs no more thought than 
processing a string which is composed of a language which is written 
left-to-right - because (logically - in terms of how humans process it 
themselves) there is no difference.


All apparent 'difficulties' and 'oddness' which dealing with non 
left-to-right text are confined solely to the presentation layer - which 
at the level of rendering text, LiveCode does for you.


This is important to remember if you are involved in localisation 
applications to languages such as Arabic - the main work you have to do 
is getting the translations in the first place, and *potentially* making 
your app right-to-left dominant, rather than left-to-right (i.e. labels 
should go on the right of fields, rather than the left, and things 
should generally be aligned to the right, rather than the to the left - 
although the actual alignment of text within fields  / buttons etc. will 
'do the right thing').


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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-livecode

Re: How to to type bottom to up and right to left in a field

2017-09-21 Thread Jonathan Lynch via use-livecode

Maybe share a sample stack when you get it worked out? This could be useful for 
users in places that use right-to-left text. We could with sticking points that 
way.

Sent from my iPhone

> On Sep 21, 2017, at 2:03 PM, Mark Waddingham via use-livecode 
>  wrote:
> 
> dominant

___
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-livecode

Re: How to to type bottom to up and right to left in a field

> Craig wrote:
> The textChanged handler sort of works. If you leave the field and replace the 
> cursor, the next char goes after the currently selected line. From then on it 
> goes before the current text.The backspace key does not really work.

Hey, of course it works. When editing it deletes one char at a time, when 
typing it deletes everything before the first char ;-)
___
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-livecode

Re: How to to type bottom to up and right to left in a field

> R.G. wrote
> Indeed it does. At first glance the behavior seems at least 
> unintuitive. It also appears to prevent the Backspace key from having 
> any effect. Is it a bug?  A feature?

You can also edit one char at a time.

Isn't that a feature for right to left languages?
One has simply to work a little bit harder to do the right to left top to down.


___
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-livecode

Re: How to to type bottom to up and right to left in a field

Of course it is essentially:

on textchanged
  select before me
end textchanged

___
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-livecode

Re: Setting the acceleratedRendering to true on startup on Android 7 and Android 8

I have a Pixel that was just updated to Oreo (Android 8) and running 
Swami's app works okay. That's the one app I happen to have installed 
that uses acceleratedRendering quite a bit.


He's made some changes recently that turns it on and off after the card 
has already loaded, but on some cards it loads on preOpenCard or 
preOpenStack. I guess I should poke around and see where those cards are 
so I can test it again for you.


On 9/20/17 5:04 PM, panagiotis merakos via use-livecode wrote:

Hi Jacque,

Are you on Android 7 or 8? It does not work for me if I set the
acceleratedRendering in preopenstack or openstack. I did not check with
opencard/preopencard.

On Wed, Sep 20, 2017 at 10:13 PM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:


Does it work if you set acceleratedRendering in preOpenStack or
preOpenCard? It seems to work okay for me that way.


On 9/20/17 5:21 AM, panagiotis merakos via use-livecode wrote:


Hi folks,

Today I came across this issue, affecting Android 7 and Android 8:

on openStack
 set the acceleratedRendering of this stack to true
end openStack


This results in black screen when the app starts.


Workaround:

on openStack
send "fixit" to me in 0 millisec
end openStack

on fixit
set the acceleratedRendering of this stack to true
end fixit

I'll file a report soon.

Hope this helps,
Panos
—
___
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-livecode




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
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-livecode

___
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-livecode




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
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-livecode

Re: How to to type bottom to up and right to left in a field

2017-09-21 Thread Mark Waddingham via use-livecode


On 2017-09-21 18:48, Richard Gaskin via use-livecode wrote:

Indeed it does.  At first glance the behavior seems at least
unintuitive.  It also appears to prevent the Backspace key from having
any effect.  Is it a bug?  A feature?

Hmmm...

On further consideration it may make sense, since the selection is
removed by replacing the field contents, and the default selection is
at the beginning of a line.


Indeed!

When you do 'replace x with y in ' then the engine:

  1) Fetches the text of the field as a string

  2) Performs replace x with y on that string

  3) Sets the text of the field to the modified string

Whenever a range of text is set in a field, the selection is set to the 
beginning of the chunk that was set - so in the case of 'replace' acting 
on the whole field, that would be the beginning.


Using the '(replacing | preserving) styles' form works slightly 
differently - it iterates through the content of the field, and only 
mutates the parts which are to be replaced. So with that form, the 
selection index would end up being the beginning of the last occurrence 
of x which was replaced with y.


The rule is relatively sensible I think - since if a range of text is 
replaced, the only index you can guarantee will be in the same place as 
it was before is the beginning of the range which was replaced...


Although it does give a somewhat amusing outcome in this case :)


It would seem the only way to preserve the insertion point would be to
separately trap for all relevant messages (backspaceKey, pasteKey,
dragDrop, keyDown, etc.), where you first query the selectedChunk,
perform the action, then adjust the selectedChunk according to the
length of the operation, and then restore the insertion point at the
adjusted offset.


Yes - I can't think of an alternative approach at the moment which would 
be easier. The textChanged message is a bit of a blunt instrument - 
mainly because it was the best we could add to the field at the time 
without potentially ending up down a whole set of rabbit warrens, or 
impacting performance too much.



This seems like so many things in a good scripting language:  when you
want to do something ordinary, the provided behaviors make the task
uncommonly easy.  But when you want to do something extraordinary, the
task is uncommonly difficult.


Of course one question to ask here is - what are the use cases where you 
need to preserve the selection index where the 'set it to the beginning 
of the last replaced chunk' isn't appropriate? If script is doing the 
mutation, then it can happily save / restore the index itself - so it 
would come down to user-interaction cases - finding out about those 
would probably help pin down what the field could do to make things 
easier.




Incidentally whilst the above has the effect of writing bottom to top / 
right to left it is only a superficial effect as the order of the chars 
ends up being 'the wrong way round' in the internal string. Regardless 
of the writing system, humans still (I believe at least...) always 
process language in spoken order, which is the same as the order we read 
in - the fact some languages are right to left, bottom to top, right to 
left to right to left etc. is 'merely' a presentation / visual thing.


For example, let's say you have a right to left language FOO which has 
letters A, B, C; compared to a left to right language BAR which has 
letters X, Y and Z. Hello in FOO is spoken A-B-C; Hello in BAR is spoken 
X-Y-Z. However, as FOO is right to left, Hello is written CBA. If these 
languages were mixed in a single piece of text - spoken as A-B-C X-Y-Z - 
then in memory the order would be ABC XYZ, but visually it would appear 
as either:


  i) from the left edge - CBA XYZ

  ii) from the right edge - XYZ CBA

Whether it would be (i) or (ii) depends on which is considered to be the 
dominant language in that case and context.




Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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-livecode

Re: Scrolling Groups on Mobile - Show a little of what is below


On 9/20/17 11:36 PM, Sannyasin Brahmanathaswami via use-livecode wrote:

the proper way to do it is, says Jacque: create the rows so the bottom one is a 
bit cut off, otherwise a subset of users never try to scroll up!


I'm not sure how proper it is, but it's what I do and it seems to work. 
I hadn't thought of the idea of flashing the scrollbar indicator, that 
may work as well though it would depend on how observant the user is and 
whether they understand what it means.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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-livecode

Re: How to to type bottom to up and right to left in a field

2017-09-21 Thread dunbarx via use-livecode

Well it just goes to show that I do need a computer. Mental scripting only
sounds, er, sound.

This works:

on keyDown, tKey 
   if the shiftkey is down and the capsLockKey is down then put tKey &
return before me 
   else put tKey before me
select before me
end keyDown

All the other "control" keys likely have their own functionality, and I did
not want to fiddle with them.

The textChanged handler sort of works. If you leave the field and replace
the cursor, the next char goes after the currently selected line. From then
on it goes before the current text.The backspace key does not really work.

But now we come to the real question. 

Ahem.

How does the textChanged handler work at all



--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
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-livecode

Re: How to to type bottom to up and right to left in a field

2017-09-21 Thread dunbarx via use-livecode

Well, at least this explains it:\


"...essentially"

on textchanged 
  select before me 
end textchanged 



--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
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-livecode

How to to type bottom to up and right to left in a field

Because "textChanged" was also mentioned in a recent thread.
This is a handler full of features:

*** How to to type bottom to up and right to left in a field ***

Simply script the field as follows and start typing.

on textChanged
  replace space with space in me -- or whatever
end textChanged

Doesn't work, of course, with pasted text or insertions by script.

___
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-livecode

Re: Constraining an input field's contents to be a single line.