Re: ANN: LC Documentation Cache Cleaner

2018-09-03 Thread Mark Wieder via use-livecode

On 09/03/2018 04:35 PM, J. Landman Gay via use-livecode wrote:
I found it, simple oversight I think. The mouseUp in the button doesn't 
set the hilite. Easy to fix.


My bad - I actually uploaded an earlier version (and it explicitly set 
the hilite to true. New fixed version uploaded now. In my defense... 
well, I don't really have a defense: this was slapped together in about 
a half-hour of programming, and I should know better.


--
 Mark Wieder
 ahsoftw...@gmail.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: ANN: LC Documentation Cache Cleaner

2018-09-03 Thread J. Landman Gay via use-livecode
I found it, simple oversight I think. The mouseUp in the button doesn't set 
the hilite. Easy to fix.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On September 3, 2018 5:38:06 PM Mark Wieder via use-livecode 
 wrote:



On 09/03/2018 01:56 PM, J. Landman Gay via use-livecode wrote:


Maybe run it on a Mac, I wasn't able to unhilite the verify button.

Well, that's distressing. I did try it on osx before releasing it, but
I'll go back and check it again - may have skipped a version.

--
--
 Mark Wieder
 ahsoftw...@gmail.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: ANN: LC Documentation Cache Cleaner

2018-09-03 Thread Mark Wieder via use-livecode

On 09/03/2018 01:56 PM, J. Landman Gay via use-livecode wrote:

Maybe run it on a Mac, I wasn't able to unhilite the verify button. 
Well, that's distressing. I did try it on osx before releasing it, but 
I'll go back and check it again - may have skipped a version.


--
--
 Mark Wieder
 ahsoftw...@gmail.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: ImageHandles_v105

2018-09-03 Thread tbodine via use-livecode
I will definitely check this out. 
Thanks!
Tom B.



--
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: Mobile Rotation Redux

2018-09-03 Thread Brian Milby via use-livecode
Thanks for running the tests!

I've been working on this stack for the past 2 days.  I've made quite a bit
of progress and switched to using the new handler to set orientation
rects.  That simplifies things a bit.  I had to write some code to figure
out the rect to use for device native though (which wouldn't be an issue
for a real app since your rect would be fixed at design time).

The math is required because you need to translate the rect.  The
screenrect is absolute for the device.  The graphic rect is relative to the
card.  This is only needed for the "showAll" fullscreenmode.

I'm planning on turning the button position action into a group behavior.
Once I get that done, I'll post an update.

Thanks,
Brian

On Mon, Sep 3, 2018 at 4:24 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I ran both stacks on my Pixel and they got exactly the same results you
> reported; in other words, everything worked just fine.
>
> I decided to try my theory that we could combine fullscreenMode with
> individual object placement and we can. This will prevent the tiny image
> when the device is rotated to landscape. Basically, for a stack that is
> taller than it is wide, you want showAll in portrait and noBorder in
> landscape. All I had to do was revise your orientationChanged handler
> and add some logic to determine the correct fullscreenMode. I suspect
> mobileSetFullScreenRectForOrientations would do the same thing, but I
> wasn't focused on that.
>
> So in the MobileDemo stack, revise orientationChanged and add the FSM
> function and it should work. The rest of the handlers can remain as-is.
> This particular revision only assumes we're using showAll and noBorder;
> it doesn't address any others. Those are the two that almost all mobile
> apps use.
>
> on orientationChanged
>if the fullscreenmode of this stack is not empty then
>  send "setBackground" to me in 200 milliseconds
>  send "setFSM" to me in 250 milliseconds
>  -- updateStatus "Orientation:" && mobileDeviceOrientation()
>end if
> end orientationChanged
>
> on setFSM
>if the fullscreenmode of this stack is not among the items of
> "showAll,noBorder" then exit setFSM
>set the rect of this stack to the effective working screenRect
>if mobileDeviceOrientation() contains "landscape" then
>  set the fullscreenmode of this stack to "noBorder"
>else if mobileDeviceOrientation() contains "portrait" then
>  set the fullscreenmode of this stack to "showAll"
>end if
>updateStatus "setFSM:" && the fullscreenmode of this stack
>set the backcolor of this cd to the backcolor of this cd
> end setFSM
>
> I had to use your "set the rect of this stack" method to force
> fullscreenMode to resolve, that's a nice trick. Setting the backcolor of
> the card to its existing color is a hack workaround that Panos
> discovered which forces a card redraw. That eliminates the issue where
> objects outside the card rect don't redraw properly, so now you don't
> need to lay the device flat to do it.
>
> I did wonder why you need the math in the setBackground handler. Doesn't
> the working screenrect give the right measurements?
>
>
> On 9/1/18 1:35 AM, Brian Milby via use-livecode wrote:
> > As I like to do, I decided to really over-do the demo test stacks.  The
> one
> > I mentioned initially is:
> >
> > https://milby.us/lc/RotationDemo.livecode
> >
> > The one I just finished working on does a bit more:
> >
> > https://milby.us/lc/MobileDemo.livecode
> >
> > I built both to test resizeStack and rotation on Android.  I only have a
> 5"
> > Fire, so I only was able to test on one device.
>
> --
> 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: Mobile Rotation Redux

2018-09-03 Thread J. Landman Gay via use-livecode
I ran both stacks on my Pixel and they got exactly the same results you 
reported; in other words, everything worked just fine.


I decided to try my theory that we could combine fullscreenMode with 
individual object placement and we can. This will prevent the tiny image 
when the device is rotated to landscape. Basically, for a stack that is 
taller than it is wide, you want showAll in portrait and noBorder in 
landscape. All I had to do was revise your orientationChanged handler 
and add some logic to determine the correct fullscreenMode. I suspect 
mobileSetFullScreenRectForOrientations would do the same thing, but I 
wasn't focused on that.


So in the MobileDemo stack, revise orientationChanged and add the FSM 
function and it should work. The rest of the handlers can remain as-is. 
This particular revision only assumes we're using showAll and noBorder; 
it doesn't address any others. Those are the two that almost all mobile 
apps use.


on orientationChanged
  if the fullscreenmode of this stack is not empty then
send "setBackground" to me in 200 milliseconds
send "setFSM" to me in 250 milliseconds
-- updateStatus "Orientation:" && mobileDeviceOrientation()
  end if
end orientationChanged

on setFSM
  if the fullscreenmode of this stack is not among the items of 
"showAll,noBorder" then exit setFSM

  set the rect of this stack to the effective working screenRect
  if mobileDeviceOrientation() contains "landscape" then
set the fullscreenmode of this stack to "noBorder"
  else if mobileDeviceOrientation() contains "portrait" then
set the fullscreenmode of this stack to "showAll"
  end if
  updateStatus "setFSM:" && the fullscreenmode of this stack
  set the backcolor of this cd to the backcolor of this cd
end setFSM

I had to use your "set the rect of this stack" method to force 
fullscreenMode to resolve, that's a nice trick. Setting the backcolor of 
the card to its existing color is a hack workaround that Panos 
discovered which forces a card redraw. That eliminates the issue where 
objects outside the card rect don't redraw properly, so now you don't 
need to lay the device flat to do it.


I did wonder why you need the math in the setBackground handler. Doesn't 
the working screenrect give the right measurements?



On 9/1/18 1:35 AM, Brian Milby via use-livecode wrote:

As I like to do, I decided to really over-do the demo test stacks.  The one
I mentioned initially is:

https://milby.us/lc/RotationDemo.livecode

The one I just finished working on does a bit more:

https://milby.us/lc/MobileDemo.livecode

I built both to test resizeStack and rotation on Android.  I only have a 5"
Fire, so I only was able to test on one device. 


--
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: ANN: LC Documentation Cache Cleaner

2018-09-03 Thread Jim Lambert via use-livecode
Mark,

Very handy!

Thanks,
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: ANN: LC Documentation Cache Cleaner

2018-09-03 Thread J. Landman Gay via use-livecode

On 9/2/18 1:21 PM, Mark Wieder via use-livecode wrote:

Posted a utility stack to livecodeshare:

When first launched, the LiveCode IDE will build a documentation cache 
for the current version. When you upgrade to a new version, a new cache 
folder is created, but any older cache is still in the system. When you 
remove an older LiveCode version the cache folder is not removed, so 
these accumulate over time.


This stack will allow you to remove any documentation cache folders that 
are no longer needed in order to reclaim storage space on your computer. 
If you remove a current one accidentally it will be rebuilt the next 
time the LiveCode IDE is launched.


http://livecodeshare.runrev.com/stack/895/LC-Documentation-Cache-Cleaner



Wow, I had no idea. I must have had 30 or 40 of those.

Maybe run it on a Mac, I wasn't able to unhilite the verify button. 
Forty dialogs is a bit much. I hit the return key repeatedly and the 
backed up queue must have confused it because eventually it stopped 
deleting things. I unhilited the button in the property inspector and 
after that things went much faster.


But this is still a fantastic tool, thanks much.

--
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: Where's Fraser?

2018-09-03 Thread J. Landman Gay via use-livecode

On 9/3/18 10:57 AM, Mark Wieder via use-livecode wrote:

On 09/03/2018 06:53 AM, Lagi Pittas via use-livecode wrote:

In the spirit of where's wally

Can you spot Fraser in this Pic?

https://www.dejero.com/about-us/profile


Ha! Well, that certainly looks like Fraser. Is that really him?


Gotta be. Who else would camouflage himself that way? :)

--
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: Where's Fraser?

2018-09-03 Thread Mark Wieder via use-livecode

On 09/03/2018 06:53 AM, Lagi Pittas via use-livecode wrote:

In the spirit of where's wally

Can you spot Fraser in this Pic?

https://www.dejero.com/about-us/profile


Ha! Well, that certainly looks like Fraser. Is that really him?

--
 Mark Wieder
 ahsoftw...@gmail.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


Where's Fraser?

2018-09-03 Thread Lagi Pittas via use-livecode
In the spirit of where's wally

Can you spot Fraser in this Pic?

https://www.dejero.com/about-us/profile

Hint - there are only 2 that can be even considered.

Regards Lagi
___
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: Searching for a word when it's more than one word

2018-09-03 Thread David V Glasgow via use-livecode
My family was stranded for a while during a transfer at Frankfurt airport, 
while  a computer system refused to accept that ‘Glasgow’ was not a 
destination. ( At least, in that instance)

Having said that, the same error is much more commonly made by taxi drivers, 
who can’t avoid showing great disappointment, when I am just going to the local 
station.

Cheers,

David Glasgow

> On 1 Sep 2018, at 5:57 pm, Richmond Mathewson via use-livecode 
>  wrote:
> 
> That sounds remarkably like two women who are friends of my parents:
> 
> One is called "Gay" and the other one is called "Loveday". They were friends 
> at school 60 years ago
> and when they were both widowed they moved in together; although the son of 
> one of them fell out
> with his wife and now lives with them as well.
> 
> Assumptions are sometimes difficult to avoid.
> 
> Although my younger son did actually dislocate his knee jumping to 
> conclusions . . .
> 
> This was mainly because he was trying to skip a difficult bit . . .
> 
> But I digress.
> 
> Richmond.
> 
> On 1/9/2018 6:39 pm, J. Landman Gay via use-livecode wrote:
>> There is a town in Texas called West, made infamous a few years ago by a 
>> giant explosion. I don't think you can make assumptions about names of 
>> places.
>> 
>> Mark's suggestion to check for words ending in "s" will fail on many towns, 
>> though apostrophe-s may be safe.
>> -- 
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On September 1, 2018 5:49:30 AM Richmond Mathewson via use-livecode 
>>  wrote:
>> 
>>> I can see that the "problem", which my stack does not address, is with 2
>>> or 3 part place names:
>>> 
>>> The Rochester/Chester problem is easily dealt with.
>>> 
>>> While it should be realtively easy to have a subroutine to deal with
>>> words such as "West" (after all, there are no places just called "West"),
>>> places like a town my parents once lived in called "Haselbury Plucknett"
>>> would cause problems.
>>> 
>>> AND, places such as "Ruyton of the Eleven Towns"
>>> (https://en.wikipedia.org/wiki/Ruyton-XI-Towns)
>>> would really throw a spanner in the works.
>>> 
>>> Come to think of things . . .
>>> 
>>> Unless anyone's code can cope with "Ruyton of the Eleven Towns" it won't
>>> stand up: we could even go further and call
>>> this the "Ruyton of the Eleven Towns Test".
>>> 
>>> More muffled background noises.
>>> 
>>> Richmond.
>>> 
>>> On 1/9/2018 1:29 pm, Mark Waddingham via use-livecode wrote:
 On 2018-09-01 12:05, Richmond Mathewson via use-livecode wrote:
> Obviously, when considering names of places such as Colchester,
> Rochester and Chester one has
> to search for the longer names first and exclude them from later
> searches.
 
 The 'substring' problem (i.e. Chester being 'in' Rochester) isn't
 relevant in the above algorithm because we are 'tokenising' input and
 phrases - essentially changing the alphabet.
 
 i.e. "Rochester Chester Colchester" is turned into ABC, and we match
 A, B or C as atomic units.
 
 I should perhaps point out that the 'processText' operation probably
 needs to be a little better in practice - to at least include a 'stop'
 token for punctuation. For example:
 
 "The man walked starting from East Hartford, West Hartford could be
 seen in the distance."
 
 In the case where 'Hartford West' and 'Hartford' are the 'known' towns
 (and not 'East Hartford') - the proposed tokenization would result in:
 
 The,man,walked,starting,from,East,Hartford,West,Hartford,could,be,seen,in,the,distance
  
 
 Which means you'd get "Hartford West" and "Hartford" - when you should
 only get "Hartford" (assuming you care about the linguistic structure
 of the text, at least).
 
 Indeed, the above actually means in preprocessing the text, you can
 actually vastly reduce the number of words to search - any sequences
 of words which aren't in any pharse (or important punctuation) can be
 replaced by "*" say. So the above would become:
 
 *,East,Hartford,*,West,Hartford,*
 
 The "*" tokens block matching multi-word phrases.
 
 Warmest Regards,
 
 Mark.
>>> 
>>> ___
>>> 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, unsub

Re: ANN: LC Documentation Cache Cleaner

2018-09-03 Thread Matthias Rebbe via use-livecode
Mark, thanks for this. 

Couldn´t believe how many cache folders existed on my harddrive.

Regards,

Matthias


> Am 02.09.2018 um 20:21 schrieb Mark Wieder via use-livecode 
> :
> 
> Posted a utility stack to livecodeshare:
> 
> When first launched, the LiveCode IDE will build a documentation cache for 
> the current version. When you upgrade to a new version, a new cache folder is 
> created, but any older cache is still in the system. When you remove an older 
> LiveCode version the cache folder is not removed, so these accumulate over 
> time.
> 
> This stack will allow you to remove any documentation cache folders that are 
> no longer needed in order to reclaim storage space on your computer. If you 
> remove a current one accidentally it will be rebuilt the next time the 
> LiveCode IDE is launched.
> 
> http://livecodeshare.runrev.com/stack/895/LC-Documentation-Cache-Cleaner
> 
> -- 
> Mark Wieder
> ahsoftw...@gmail.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

[ANN] This Week in LiveCode 144

2018-09-03 Thread panagiotis merakos via use-livecode
Hi all,

Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!

Read issue #144 here: https://goo.gl/KYVehE

This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around the open source project. New issues will be
released weekly on Mondays. We have a dedicated mailing list that will
deliver each issue directly to you e-mail, so you don't miss any!

If you have anything you'd like mentioned (a project, a discussion
somewhere, an upcoming event) then please get in touch.


-- 
Panagiotis Merakos 
LiveCode Software Developer

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: ImageHandles_v105

2018-09-03 Thread panagiotis merakos via use-livecode
Thanks Hermann :)

On Sat, Sep 1, 2018 at 7:28 PM hh via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Just uploaded hhImageHandles to "Sample Stacks".
>
> This is a group of handles that is attachable to any image.
> All you have to do (after copying the group to your stack):
> send "setTarget " to group "hhPoly"
>
> Base position of the 9 handles (use a monospaced font):
>###
>## 1 ##
>## | ##
>## 9 - 2 - 3 ##
>## |   | ##
>## 8   4 ##
>## |   | ##
>## 7 - 6 - 5 ##
>###
> Actions:
> a=Click and drag, b=Shift-Click or RightClick and drag
>
> 1: (a) Rotate, (b) Reset shape
> 2,6: (a) Height, (b) SkewX
> 4,8: (a) Width,  (b) SkewY
> 3,5,7,9: (a) 4-Point-Distortion
> 3,5,7,9: (b) ProportionalResize
>
> Rotation is around the shapes's centroid (which can also be shown).
>
> Changing height, width or proportional resizing preserves the
> current shape!
>
> hhImageHandles works on Mac/Win/Linux and comes in two variants.
>
> [1] livecodeshare.runrev.com/stack/893
> hhImageHandles6_LCS (pure LCScript) is for LC 6/7/8/9,
> fast enough (only) on LC 6.
>
> [2] livecodeshare.runrev.com/stack/894
> hhImageHandles89B has the option to use JavaScript (of a browser
> widget) and is with that at about 15-20 faster as LCS.
>
>
> ___
> 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: Trouble with iOS Logos/No Appearing on Home Screen

2018-09-03 Thread panagiotis merakos via use-livecode
Hello Brahmanathaswami,

If you only see the default icon, then you might need to download Xcode's
additional components.

See https://quality.livecode.com/show_bug.cgi?id=21531

also, why would you check (uncheck) Prerendered choice?

This was needed for some older iOS versions (I think less than iOS 5), so
this option now is not needed anyway. We probably have to remove it from
the standalone settings.

Best,
Panos
--



On Sat, Sep 1, 2018 at 4:00 AM Sannyasin Brahmanathaswami via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I have tried everything, the logos in the standalone maker are as they
> are supposed to be, according to SA. And so are my splash screen images.
>
> So I went to developer.apple.com
>
> And the HIG  for app icons (and splash screens) give a different set of
> sizes.
>
> So I downloaded "Icon Set  Creator" (free)  and it produced these. Which
> do in fact correspond to the current guide at developer.apple.com
>
> Note as an example,  SivaSiva logo...@2x.png corresponds with iPhone
> icon. That would be 58px , but the standalone maker wants a 57 size icon.
>
> SivaSiva Logo-1024.png
> SivaSiva Logo-20.png
> SivaSiva logo...@2x.png
> SivaSiva logo...@3x.png
> SivaSiva Logo-29.png
> SivaSiva logo...@2x.png
> SivaSiva logo...@3x.png
> SivaSiva Logo-40.png
> SivaSiva logo...@2x.png
> SivaSiva logo...@3x.png
> SivaSiva logo...@2x.png
> SivaSiva logo...@3x.png
> SivaSiva Logo-76.png
> SivaSiva logo...@2x.png
> SivaSiva logo-8...@2x.png
>
> 1.2.2 is ready for the app store, only this one problem!
>
> also, why would you check (uncheck) Prerendered choice?
>
> ??
>
>
> ___
> 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: Android Audio Recorder Woes

2018-09-03 Thread panagiotis merakos via use-livecode
Hello Dan,

Hehe no worries, you're welcome. The Android Audio Recorder Lib is
currently the only case where you'll have to ask for a permission
explicitly. In all other cases (including Location) the permission dialog
is shown automatically.

For example, RE location access, if you call
, this will first ask for location
permission.

Kind regards,
Panos
--

On Sat, Sep 1, 2018 at 12:27 AM Dan Friedman 
wrote:

> Panos,
>
>
>
> Ug!  Yes, that was it.  I feel especially stupid because I already did it
> for Location Access.   Must be Friday!?!
>
>
>
> Thank you!
>
>
>
> -Dan
>
>
>
>
>
> *From: *panagiotis merakos 
> *Date: *Friday, August 31, 2018 at 1:34 PM
> *To: *Dan Friedman 
> *Cc: *How to use LiveCode 
> *Subject: *Re: Android Audio Recorder Woes
>
>
>
> Hello Dan,
>
>
>
> Ok, so since 9.0.1 uses the new android permissions model, you might have
> to ask for permission to record audio first. See the command
> androidRequestPermission in the dictionary.
>
>
>
> Best,
>
> Panos
>
>
>
> On Fri, Aug 31, 2018, 23:30 Dan Friedman  wrote:
>
> Panos.
>
>
>
> Thank you for the reply!  I am using LC  9.0.1 (rc 2).
>
>
>
>
>
> Thank you!
>
>
>
> Dan Friedman
>
> CEO, ClearVision Technologies, LLC
>
> Voice: 909/484-2052
>
> http://www.clearvisiontech.com
>
>
>
>
>
> *From: *panagiotis merakos 
> *Date: *Friday, August 31, 2018 at 1:27 PM
> *To: *How to use LiveCode 
> *Cc: *Dan Friedman 
> *Subject: *Re: Android Audio Recorder Woes
>
>
>
> Hello Dan,
>
> Which LC version are you using?
>
>
>
> Best,
>
> Panos
>
>
>
> On Fri, Aug 31, 2018, 18:51 Dan Friedman via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> Hello!   I am trying to implement the Android Audio Recorder options in my
> project, but it’s not working.  I have checked the “Android Audio Recorder”
> in the Standalone Application Settings, and the called this:
>
> androidRecorderSetRecordFormat "MPEG-4"
> put (specialFolderPath("documents") & "/ test.mp4") into fPath
> androidRecorderStartRecording fPath
>
> The androidRecorderSetRecordFormat seems to be ok as it’s failing on the
> androidRecorderStartRecording call.   Is there something else I need to do
> or set to get this working?
>
> Thanks in advance
> -Dan
> ___
> 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