Would Anyone Like a Ring Tone At End of Standalone Built?

2018-05-19 Thread Sannyasin Brahmanathaswami via use-livecode
with Android, it fast enough, but building to iOS … I have enough time to do 
email…

I you use spaces.
You won't knon when the build is finished.

Would any else like a ring tone when the SA is finished?

I wonder if I could hack the IDE to do that..

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

Re: Transition from DataGrid in existing app to DataGrid 2 in LC 9.0

2018-05-19 Thread zryip theSlug via use-livecode
Martin,

The already existing data grid controls will work directly with the new
library. You have nothing to change or to re-install. All the handlers,
functions or properties of the datagrid API are still existing in the dg2
Library even if they have been rewrote. The only problem I encounter was
with deleteLine I used for deleting several lines at a time despite the
documentation recommandation. I changed the entry for deleteLines to fix
things.

On Thu, May 17, 2018 at 3:06 PM, Martin Koob via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi
>
> I have a Mac OS X application that is developed with LC 6.7.3 that I am
> transitioning to LC 9.0.
>
> I have some form style DataGrids in the application.   When I open the
> project in the LC 9.0 IDE do these data grids automatically have the new
> features of DataGrid 2 or do I have to replace the DataGrids with new ones
> to get all the DataGrid 2 features.
>
> Any other hints on transitioning DataGrids would be appreciated.
>
> Thanks.
>
> Martin Koob
>
>
>
>
> --
> 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
>



-- 
Zryip TheSlug
http://www.aslugontheroad.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


More Long ID Differences

2018-05-19 Thread Brian Milby via use-livecode
I found another example where the long id of an object is different
depending on whether the card has been visited or not.  The following
command in the message box:

put the long id of button id 1015 of stack "ScriptTrackerPrefs" of stack
"ScriptTracker"

Will generate 2 different results:

button id 1015 of stack "ScriptTrackerPrefs" of stack
"[snip]/ScriptTracker.livecode"

button id 1015 of card id 1005 of stack "ScriptTrackerPrefs" of stack
"[snip]/ScriptTracker.livecode"

The first is what I get when opening the stack, before I have visited any
cards.  Objects on the first card will always get the second results.
After making the stack visible and visiting the card, the second result
will always be returned (regardless of the current card).

This is obviously related to the background issue identified earlier.  If a
card containing a background has never been visited, then "bkgnd xxx" is
found in the long id.  If it has, then "group xxx of card yyy" is found in
the long id.  This similarly changes objects within those groups as well.

I'm sure this doesn't matter to most developers as it does not effect the
ability to locate an object and interact with it.  If, however, you are
counting on the card being identified in the long id it may.  For my stack,
I'm putting the long id in the script header and this causes diffs when
there shouldn't be any (think Git).  In the case of objects that are not in
a background group, I do want the card reference.  On the flip side, if in
a background then I don't.

I'll be expanding my code to handle this difference.  Since I'm working my
way down from stack to control, it will be easy to maintain the parent
portion of my long id/name.  If importing, then I will just use the
previous long id/name.

If you want to take a look, the code is here:
https://github.com/bwmilby/lc-misc/tree/master/ScriptTracker

Cheers,
Brian
___
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: Signing MacOS Standalones

2018-05-19 Thread Ray via use-livecode

Many thanks Paul - I'll give this a try and post how it works out.


On 5/19/2018 1:47 PM, Paul Dupuis via use-livecode wrote:

You will still have to join Apple Developer to purchase a certificate,
but then use AppWrapper (http://www.ohanaware.com/appwrapper/)

On 5/19/2018 5:19 AM, Ray via use-livecode wrote:

Does anybody have steps to sign Mac OS standalones?  I've discovered
Apple 10.12 or higher now sabotages unsigned standalones and it's a
rather cryptic process to join the Apple dev club, create a
certificate, and then sign an LC standalone, evidently using Terminal.

Thanks in advance!

Ray Horsley

___
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



___
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: Signing MacOS Standalones

2018-05-19 Thread Paul Dupuis via use-livecode
You will still have to join Apple Developer to purchase a certificate,
but then use AppWrapper (http://www.ohanaware.com/appwrapper/)

On 5/19/2018 5:19 AM, Ray via use-livecode wrote:
> Does anybody have steps to sign Mac OS standalones?  I've discovered
> Apple 10.12 or higher now sabotages unsigned standalones and it's a
> rather cryptic process to join the Apple dev club, create a
> certificate, and then sign an LC standalone, evidently using Terminal.
>
> Thanks in advance!
>
> Ray Horsley
>
> ___
> 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

Signing MacOS Standalones

2018-05-19 Thread Ray via use-livecode
Does anybody have steps to sign Mac OS standalones?  I've discovered 
Apple 10.12 or higher now sabotages unsigned standalones and it's a 
rather cryptic process to join the Apple dev club, create a certificate, 
and then sign an LC standalone, evidently using Terminal.


Thanks in advance!

Ray Horsley

___
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: Android API Level 26 required as of August 2018

2018-05-19 Thread J. Landman Gay via use-livecode
Thanks for the quick fix, Ali. I'll copy it for now, I'm going to need 
it next week.


On 5/18/18 3:23 PM, Ali Lloyd via use-livecode wrote:

PR: https://github.com/livecode/livecode/pull/6536

I've managed to lock myself out of Bugzilla, so will finish it off when
I've reported a bug! But obviously the patch can be applied locally if
anyone needs it urgently.

On Fri, May 18, 2018 at 9:05 PM Ali Lloyd  wrote:


Currently the merge only takes the maximum of the provided minimum SDK
versions, which is something of an oversight. However it's an easy patch to
ensure it takes the maximum of the target versions too - I will submit a PR
shortly.


On Fri, May 18, 2018 at 8:17 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:


Answering myself, the target version is already included in the Android
manifest that LC uses by default. It is set to be the same as the
minimum version. We can edit that to use a different number. Make a copy
of the default manifest, located at:
/Contents/Tools/Runtime/Android/Manifest.xml

Change this:


To this:


Then include the revised manifest in the Copy Files pane of the
standalone settings. In LC versions prior to LC 9 it will replace the
default one when you do a build. In LC 9, the standalone builder now
merges your manifest with the default template.

I'm not entirely clear how the merging works, but it sounds like you
could create a manifest with only the changes you want to implement. For
now I'll just edit the template and assume LC will find which edits to
include. If anyone knows for sure, I'd like to hear how it works exactly.


On 5/18/18 1:42 PM, J. Landman Gay via use-livecode wrote:

I brought this up on the list a while ago. The target version is
different from the minimum version I think, and there's no way to
specify a target in standalone settings. I think we'll need to create
our own manifest that includes the target. I'll have to look up how to
do that, I'm not sure yet what to include.

This will affect me too, since I need to upload to the Play Store in a
couple of days.

On 5/18/18 12:45 PM, bob--- via use-livecode wrote:

I posted an APK to the Google Play Store today for another project I
work on (not LC based) and received a warning that I've not seen
before (1 week ago the same App not receive this warning).

"Target API level requirements from August 2018
Warning:
Your app currently targets API level 25 and must target at least API
level 26 to ensure it is built on the latest APIs optimized for
security and performance.


 From August 2018, new apps must target at least Android 8.0 (API
level 26).
 From November 2018, app updates must target Android 8.0 (API level

26).

Tip:
Change your app's target API level. Learn how."

Some months ago I attempted to build for Android on LC I ran into
problems until I used an older version of either the API???/ SDK???
(not sure what right now). I'm posting this here just as an FYI and to
see if anyone might now if this is something we need to worry about in
the LC space.

I didn't want to open a QC report until someone can confirm/deny this
is an issue or not.

Thanks in advance,
Bob Hall


___
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