Re: LC9.6 Android EXIF image data issue

[Monte Goulding via use-livecode]

Hi Alan

EXIF data from the returned photo in mobilePickPhoto probably shouldn’t be 
relied upon. On iOS it definitely won’t be there. On Android it definitely 
won’t be there if calling mobilePickPhoto with width and height parameters but 
if those parameters aren’t used it might be there (depending on what the camera 
app does).

Cheers

Monte

> On 13 May 2020, at 11:39 am, Alan Stenhouse via use-livecode 
>  wrote:
> 
> There seems to be an issue with getting EXIF data from images using 
> mobilePickPhoto on Android (well, at least new Samsung mobile phones).
> 
> I *think* this is a new bug with LC 9.6, but as I don't have a relevant phone 
> to test with, it's sorta difficult to check further. Particularly as we 
> couldn't even use mobilePickPhoto on these phones prior to 9.6!
> 
> Has anyone else seen this at all? If it's a new issue then it'd be great to 
> get it resolved in the 9.6 cycle.
> 
> cheers
> 
> Alan
> ___
> 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

LC9.6 Android EXIF image data issue

[Alan Stenhouse via use-livecode]

There seems to be an issue with getting EXIF data from images using 
mobilePickPhoto on Android (well, at least new Samsung mobile phones).

I *think* this is a new bug with LC 9.6, but as I don't have a relevant phone 
to test with, it's sorta difficult to check further. Particularly as we 
couldn't even use mobilePickPhoto on these phones prior to 9.6!

Has anyone else seen this at all? If it's a new issue then it'd be great to get 
it resolved in the 9.6 cycle.

cheers

Alan
___
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: Open printing to pdf

[Phil Davis via use-livecode]

What happens if you remove the space from the file path? Does it still 
behave the same?


Phil Davis


On 5/12/20 4:23 PM, GEORGE WOOD via use-livecode wrote:

Here is on example of what I tried:

on mouseup

put “⁩/Desktop⁩/test files/Test.pdf” into temp

open printing to pdf temp

print cd 1 from (topleft of cd 1) to (bottomright of cd 1)

close printing

put the result

end mouseup
___
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


--
Phil Davis
503-307-4363


___
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

Open printing to pdf

[GEORGE WOOD via use-livecode]

Here is on example of what I tried:

on mouseup

put “⁩/Desktop⁩/test files/Test.pdf” into temp

open printing to pdf temp

print cd 1 from (topleft of cd 1) to (bottomright of cd 1)

close printing

put the result

end mouseup
___
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

Print to pdf

[GEORGE WOOD via use-livecode]

Is the "open printing to pdf filename" not working any longer? I have tried 
everything according to the dictionary, but it always fails with the result 
being "printing failed." Any usable workarounds? Thanks for any suggestions.
___
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: mergDocCanOpen opens iOS sharing menu

[Monte Goulding via use-livecode]

Hi Ralf

It might be that `mergDocCanOpen` needs to be deprecated as it relied on a hack 
and Apple must have changed the behavior. Checking the result after 
`mergDocShow*` commands will still report if the document interaction 
controller was able to be shown for the document.

Cheers

Monte

> On 13 May 2020, at 4:07 am, Ralf Bitter via use-livecode 
>  wrote:
> 
> Seems there is an issue with mergDocCanOpen(). Whenever this function
> is called the iOS sharing menu shows up for a short moment at the top
> of the screen. I am running LC 9.6.0 (rc1) and iOS SDK 13.2. The particular
> script including this function worked fine in earlier versions.
> 
> Does anybody have a recipe to avoid this undesirable behavior?
> 
> Ralf
> 
> ___
> 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

mergDocCanOpen opens iOS sharing menu

[Ralf Bitter via use-livecode]

Seems there is an issue with mergDocCanOpen(). Whenever this function
is called the iOS sharing menu shows up for a short moment at the top
of the screen. I am running LC 9.6.0 (rc1) and iOS SDK 13.2. The particular
script including this function worked fine in earlier versions.

Does anybody have a recipe to avoid this undesirable behavior?

Ralf

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

[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 #225 here: https://bit.ly/35QGXQn

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: [ANN] Release 9.6.0 RC-1

[Ralph DiMola via use-livecode]

Monte/Mark thanks from me also! I am looking now at creating launch
storyboards. I will dig in and see what I can find.

Have a good evening.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Mark Waddingham via use-livecode
Sent: Tuesday, May 12, 2020 9:03 AM
To: How to use LiveCode
Cc: Mark Waddingham
Subject: Re: [ANN] Release 9.6.0 RC-1

On 2020-05-12 13:45, Ralph DiMola via use-livecode wrote:
> Monte/LC Team,
> 
> I understand that you have limited resources. Could there be a 
> comprise here to share the workload? Instead of LC having to support 
> and change the iOS standalone options every time there is a new iOS 
> device format we(LC USERS) could pickup this pain. If there could be 2 
> options for splash screens this could work out for all.
> 1) Users can use the present 9.6 rc1 storyboard options.
> 2) Users could supply a file of resolutions and associated image names 
> for each specific resolution the user wanted to supply a custom image 
> for. If there is not a match then the images in the current 9.6 rc1 
> standalone splash screen implementation would be used.
> 
> This would put the splash screen implementation of current and new 
> screen specs squarely in hands of the LC user while retaining the 
> current seamless transition from splash to card 1. (if the LC user 
> wanted to put in the effort).

Unfortunately I'm not sure this is possible.

Apple are (soon) going to require all apps to use a launch storyboard -
specifying launch images is no longer viable if you want your app in the
AppStore.

When we started adding storyboards I asked Monte to see if there was a way
to allow current settings to work (i.e. build a storyboard which uses the
same images currently specified in the same way), and also offer a
simplified option (which is what has transpired in 9.6)...

Unfortunately it would seem that storyboards do not allow images to be
chosen based on screen size - just device type (iPhone vs iPad) and
generalized layout types (normal vs compact) - this means there appears to
be no way to replicate what you could do with simple launch images.

Apple HIG for this is a great ideal - but in reality (as far as I can
see) the only apps which can do that are those which use only iOS native
controls (the idea is that you have a launch storyboard which contains
skeleton controls from your first screen). Any app which relies on
customized controls (even intermingled with iOS ones) cannot achieve what
Apple suggests.

What we have wasn't something we just quickly did at the last minute there
was a concerted effort (as there always is) to preserve what we already had,
but we did not manage to find a way :(

That being said, it is possible that we have missed a storyboard capability
somewhere, so if someone can figure out how to create a launch storyboard
which *does* select images based on screen size (in a similar way to launch
images work), then I can be pretty confident we will be able to generalize
it to provide similar settings to the current ones in the S/B.

Currently the plan is to (in 9.7 hopefully!) to try and allow a custom
storyboard - so you can design one in Xcode and then provide it along with
the assets it needs to the standalone builder to build into your app. We
think we can do this (there are some technical details with referencing the
assets and such) but for the reason outlined above, this still won't bring
back the much simpler 'provide many launch images' 
capability.

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


___
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] Release 9.6.0 RC-1

[scott--- via use-livecode]

Mark and Monte, thanks for clarifying.

—
Scott

> On May 12, 2020, at 6:03 AM, Mark Waddingham via use-livecode 
>  wrote:
> 
> On 2020-05-12 13:45, Ralph DiMola via use-livecode wrote:
>> Monte/LC Team,
>> I understand that you have limited resources. Could there be a
>> comprise here to share the workload? Instead of LC having to support
>> and change the iOS standalone options every time there is a new iOS
>> device format we(LC USERS) could pickup this pain. If there could be 2
>> options for splash screens this could work out for all.
>> 1) Users can use the present 9.6 rc1 storyboard options.
>> 2) Users could supply a file of resolutions and associated image names
>> for each specific resolution the user wanted to supply a custom image
>> for. If there is not a match then the images in the current 9.6 rc1
>> standalone splash screen implementation would be used.
>> This would put the splash screen implementation of current and new
>> screen specs squarely in hands of the LC user while retaining the
>> current seamless transition from splash to card 1. (if the LC user
>> wanted to put in the effort).
> 
> Unfortunately I'm not sure this is possible.
> 
> Apple are (soon) going to require all apps to use a launch storyboard - 
> specifying launch images is no longer viable if you want your app in the 
> AppStore.
> 
> When we started adding storyboards I asked Monte to see if there was a way to 
> allow current settings to work (i.e. build a storyboard which uses the same 
> images currently specified in the same way), and also offer a simplified 
> option (which is what has transpired in 9.6)...
> 
> Unfortunately it would seem that storyboards do not allow images to be chosen 
> based on screen size - just device type (iPhone vs iPad) and generalized 
> layout types (normal vs compact) - this means there appears to be no way to 
> replicate what you could do with simple launch images.
> 
> Apple HIG for this is a great ideal - but in reality (as far as I can see) 
> the only apps which can do that are those which use only iOS native controls 
> (the idea is that you have a launch storyboard which contains skeleton 
> controls from your first screen). Any app which relies on customized controls 
> (even intermingled with iOS ones) cannot achieve what Apple suggests.
> 
> What we have wasn't something we just quickly did at the last minute there 
> was a concerted effort (as there always is) to preserve what we already had, 
> but we did not manage to find a way :(
> 
> That being said, it is possible that we have missed a storyboard capability 
> somewhere, so if someone can figure out how to create a launch storyboard 
> which *does* select images based on screen size (in a similar way to launch 
> images work), then I can be pretty confident we will be able to generalize it 
> to provide similar settings to the current ones in the S/B.
> 
> Currently the plan is to (in 9.7 hopefully!) to try and allow a custom 
> storyboard - so you can design one in Xcode and then provide it along with 
> the assets it needs to the standalone builder to build into your app. We 
> think we can do this (there are some technical details with referencing the 
> assets and such) but for the reason outlined above, this still won't bring 
> back the much simpler 'provide many launch images' capability.
> 
> 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


___
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

mergGoogle source OSS'd

[Mike Kerner via use-livecode]

LC has decided to deprecate mergGoogle, which is disappointing since my
company uses it hourly to generate reports from our ERP system that our
customers can use to check up on you-name-it.
However, LC also generously agreed to OSS it, so here it is.
https://github.com/macMikey/merggoogle

-- 
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: [ANN] Release 9.6.0 RC-1

[Mark Waddingham via use-livecode]

On 2020-05-12 13:45, Ralph DiMola via use-livecode wrote:

Monte/LC Team,

I understand that you have limited resources. Could there be a
comprise here to share the workload? Instead of LC having to support
and change the iOS standalone options every time there is a new iOS
device format we(LC USERS) could pickup this pain. If there could be 2
options for splash screens this could work out for all.
1) Users can use the present 9.6 rc1 storyboard options.
2) Users could supply a file of resolutions and associated image names
for each specific resolution the user wanted to supply a custom image
for. If there is not a match then the images in the current 9.6 rc1
standalone splash screen implementation would be used.

This would put the splash screen implementation of current and new
screen specs squarely in hands of the LC user while retaining the
current seamless transition from splash to card 1. (if the LC user
wanted to put in the effort).


Unfortunately I'm not sure this is possible.

Apple are (soon) going to require all apps to use a launch storyboard - 
specifying launch images is no longer viable if you want your app in the 
AppStore.


When we started adding storyboards I asked Monte to see if there was a 
way to allow current settings to work (i.e. build a storyboard which 
uses the same images currently specified in the same way), and also 
offer a simplified option (which is what has transpired in 9.6)...


Unfortunately it would seem that storyboards do not allow images to be 
chosen based on screen size - just device type (iPhone vs iPad) and 
generalized layout types (normal vs compact) - this means there appears 
to be no way to replicate what you could do with simple launch images.


Apple HIG for this is a great ideal - but in reality (as far as I can 
see) the only apps which can do that are those which use only iOS native 
controls (the idea is that you have a launch storyboard which contains 
skeleton controls from your first screen). Any app which relies on 
customized controls (even intermingled with iOS ones) cannot achieve 
what Apple suggests.


What we have wasn't something we just quickly did at the last minute 
there was a concerted effort (as there always is) to preserve what we 
already had, but we did not manage to find a way :(


That being said, it is possible that we have missed a storyboard 
capability somewhere, so if someone can figure out how to create a 
launch storyboard which *does* select images based on screen size (in a 
similar way to launch images work), then I can be pretty confident we 
will be able to generalize it to provide similar settings to the current 
ones in the S/B.


Currently the plan is to (in 9.7 hopefully!) to try and allow a custom 
storyboard - so you can design one in Xcode and then provide it along 
with the assets it needs to the standalone builder to build into your 
app. We think we can do this (there are some technical details with 
referencing the assets and such) but for the reason outlined above, this 
still won't bring back the much simpler 'provide many launch images' 
capability.


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: [ANN] Release 9.6.0 RC-1

[Ralph DiMola via use-livecode]

Monte/LC Team,

I understand that you have limited resources. Could there be a comprise here to 
share the workload? Instead of LC having to support and change the iOS 
standalone options every time there is a new iOS device format we(LC USERS) 
could pickup this pain. If there could be 2 options for splash screens this 
could work out for all.
1) Users can use the present 9.6 rc1 storyboard options.
2) Users could supply a file of resolutions and associated image names for each 
specific resolution the user wanted to supply a custom image for. If there is 
not a match then the images in the current 9.6 rc1 standalone splash screen 
implementation would be used.

This would put the splash screen implementation of current and new screen specs 
squarely in hands of the LC user while retaining the current seamless 
transition from splash to card 1. (if the LC user wanted to put in the effort). 

Thanks for the feedback!
Have a good night...

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
Monte Goulding via use-livecode
Sent: Monday, May 11, 2020 11:40 PM
To: How to use LiveCode
Cc: Monte Goulding
Subject: Re: [ANN] Release 9.6.0 RC-1

Hi Ralph

We have had some discussions internally about the feasibility of users 
including custom storyboard file templates and imagesets. That _might_ be the 
best way forward although it could be difficult to match your UI exactly given 
storyboard does not have specific device categories but compact and regular 
width/height categories.

Cheers

Monte

> On 12 May 2020, at 12:55 pm, Ralph DiMola via use-livecode 
>  wrote:
> 
> Monte,
> 
> Thanks for the reply! But the problem I have is I want to match pixel for 
> pixel the splash page with the first card on all devices. These were my 
> customers specs. I now have to tell them this is not possible anymore. When I 
> submit an app update the splash page of the initial launch of their app will 
> be changing. This is not going to go over very well I can tell you that. Is 
> it not possible to have the storyboard code use specific images for specific 
> devices as was available in previous versions? Is this an Apple or an LC 
> limitation?
> 
> Thanks again
> 
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
> 
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On 
> Behalf Of Monte Goulding via use-livecode
> Sent: Monday, May 11, 2020 9:58 PM
> To: How to use LiveCode
> Cc: Monte Goulding
> Subject: Re: [ANN] Release 9.6.0 RC-1
> 
> Hi Ralph
> 
> The splash images are not scaled or stretched. They are centred on the launch 
> screen. You can use any size image. There’s two main options to choose from 
> here.
> 
> - use a logo PNG with transparency and rely on the background color to fill 
> the rest. You can choose from using the system background color so it 
> switches for light and dark mode or an explicit color. This is what I would 
> recommend as there’s no maintenance for new devices apple might release.
> 
> - use an image that is sized large enough to cover the entire screen in all 
> supported orientations. If supporting portrait and landscape you would need a 
> square image. As the image is not scaled you would need to update it if Apple 
> releases a larger device.
> 
> Cheers
> 
> Monte
> 
> 
>> On 12 May 2020, at 1:51 am, panagiotis merakos via use-livecode 
>>  wrote:
>> 
>> Hello Ralph,
>> 
>> I'll leave this for Monte to provide more details, but my 
>> understanding is that now with the storyboard you only need to 
>> provide one image, and this will be scaled automatically for all screen 
>> sizes.
>> 
>> So if you provide only image in the 3x slot, say a 2048x2732, the 
>> storyboard mechanism will use the same image scaled down to
>> (2048/2)x(2732/2) for the 2x  slot and (2048/3)x(2732/3) for the 1x slot.
>> 
>> So the idea is that now you do not need one separate image for each 
>> possible device size. You only need one "small", and/or one "medium"
>> and/or one "large" image, and this image (or these images, in case 
>> you provide more than one) will be used for "small","medium" and "large"
>> device screen sizes.
>> 
>> There are no specific required dimensions for each of the 1x,2x,3x 
>> slots, so you get no error message, but a rule of thumb is to use the 
>> largest image you used before for the 3x slot, and let the S/B do the rest 
>> for you.
>> 
>> *>Also, Will the image be stretched or cropped to fit the various
>> aspect*
>> *ratios?*
>> 
>> The image will be cropped.
>> 
>> If you only provide a "small" image (i.e. a 1x one), then in some 
>> large screens it might appear as a letterbox, but you can choose the 
>> background color to display in this case (in the areas that would 
>> appear "black" in the letterbox). If the description is not clear, I 
>> 

Re: [ANN] Release 9.6.0 RC-1

[scott--- via use-livecode]

Thank you for commenting, Monte,

I was very excited to hear that Livecode was moving forward with a way to 
handle the storyboard requirements.

From Apple Human Interface Guidelines 



"Design a launch screen that’s nearly identical to the first screen of 
your app. If you include elements that look different when the app finishes 
launching, people can experience an unpleasant flash between the launch screen 
and the first screen of the app.”


Using individual images allowed this to happen pretty well.

Because of differing aspect ratios, adhering to Apple's guidelines now, at 
least for apps that support both  iPhone and iPad  (or even just iPhone 6,7,8 
and iPhone X variants) seems not to be possible yet with the current 
implementation of storyboard. Not being experienced with storyboards, I’m not 
sure if this is a mismatch between Apple’s HIG documentation and storyboards in 
general or a limitation of Livecode’s early implementation of storyboards. I 
will be interested to hear how others are handling this.

--
Scott Morrow

Elementary Software
(Now with 20% less chalk dust!)
web   https://elementarysoftware.com/
email sc...@elementarysoftware.com
booth1-800-615-0867
--

> On May 11, 2020, at 8:57 PM, Monte Goulding via use-livecode 
>  wrote:
> 
> You can choose a large image designed in such a way the content on the sides 
> or top can be clipped or you can choose a smaller image and have the 
> background visible.
> 
>> On 12 May 2020, at 1:50 pm, scott--- via use-livecode 
>>  wrote:
>> 
>> I am puzzled by how we should approach this for apps that work on both 
>> iPhone and iPad? It seems we choose an iPhone image and an iPad simply has a 
>> background border around and iPhone shaped splash?
> 
> ___
> 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

AW: Externals are not loaded

[Tiemo via use-livecode]

Definitely!

-Ursprüngliche Nachricht-
Von: use-livecode  Im Auftrag von 
matthias rebbe via use-livecode
Gesendet: Montag, 11. Mai 2020 20:27
An: How to use LiveCode 
Cc: matthias_livecode_150...@m-r-d.de
Betreff: Re: Externals are not loaded

Tiemo, you're getting old... ;)

Six years ago...
http://runtime-revolution.278305.n4.nabble.com/where-does-revsecurity-dll-comes-from-td4691453.html


Regards,

Matthias

-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 11.05.2020 um 18:34 schrieb Tiemo via use-livecode 
> :
> 
> You got it!
> I have installed LC 9.0.2 32Bit and LC 9.5.1 64 Bit ...
> Obviously I have been off for too long and not anymore in the subject.
> 
> Ok, last externals question. In my old builds I found a revsecurity.dll and 
> have no idea what I have used it for and can't find it anymore in the current 
> LC setups. Can anybody  confirm that this external today is obsolete?
> 
> Thank you
> Tiemo
> 
> -Ursprüngliche Nachricht-
> Von: use-livecode  Im Auftrag 
> von matthias rebbe via use-livecode
> Gesendet: Montag, 11. Mai 2020 18:09
> An: How to use LiveCode 
> Cc: matthias_livecode_150...@m-r-d.de
> Betreff: Re: Externals are not loaded
> 
> I am not sure if this might be the problem, but what version of 9.5.1 are you 
> running? 32 or 64 bit?
> 
> If 64bit, maybe there is a problem using 32bit externals on a 64bit LC IDE 
> and you should try the 32bit version of 9.5.1. But that´s just a guess.
> 
> I would say, Panos or Mark Waddingham could answer this better.
> 
> Matthias
> 
> 
> -
> Matthias Rebbe
> Life Is Too Short For Boring Code
> 
>> Am 11.05.2020 um 17:58 schrieb Tiemo via use-livecode 
>> :
>> 
>> Hi Matthias,
>> thank you for bringing me on the right track. I forgot myself, that I 
>> changed my computer since last using this and so my LC preference 
>> file entries and my 3rd party externals were not in place.
>> 
>> BUT I am still struggling. I have on Win10 in my personal documents 
>> folder/My LiveCode/Externals/ my 3rd party externals with the propper 
>> externals.txt.
>> Now, LC 9.0.2 pics my 3rd party externals up and show them to me, 
>> when asking for: "put the externalPackages of stack "home"
>> But LC 9.5.1 ignores my 3rd party externals. Shouldn't all LC 9 
>> versions read the same prefernces file and pick the same externals? 
>> Or has anything changed in LC 9.5 with handling of externals?
>> 
>> Any idea?
>> Tiemo
>> 
>> 
>> -Ursprüngliche Nachricht-
>> Von: use-livecode  Im Auftrag 
>> von matthias rebbe via use-livecode
>> Gesendet: Montag, 11. Mai 2020 12:28
>> An: How to use LiveCode 
>> Cc: matthias_livecode_150...@m-r-d.de
>> Betreff: Re: Externals are not loaded
>> 
>> Sorry, i forgot to add the link. 
>> 
>> http://lessons.livecode.com/m/4071/l/6347-how-to-install-3rd-party-ex
>> t ernals -for-use-in-the-ide-and-standalone-builder
>> 
>> 
>> -
>> Matthias Rebbe
>> Life Is Too Short For Boring Code
>> 
>>> Am 11.05.2020 um 12:22 schrieb matthias rebbe via use-livecode
>> :
>>> 
>>> Tiemo,
>>> 
>>> are you using  the  externals that are included with LC or 3rd party ones?
>>> 
>>> If the latter, did you  check the following lesson already about How 
>>> to
>> use 3rd party Externals?
>>> 
>>> Regards,
>>> 
>>> Matthias
>>> 
>>> -
>>> Matthias Rebbe
>>> Life Is Too Short For Boring Code
>>> 
 Am 11.05.2020 um 12:04 schrieb Tiemo via use-livecode
>> :
 
 Hello,
 
 
 
 I haven't worked on this old program for a year or more, last with 
 LC
>> 9.0.2.
 It uses several externals on Windows, which are located in the standard"
 folder "Externals" within the stack folder.
 
 When I now open it with LC 9.0.2 or 9.5.1 the externalPackages of 
 the stack is empty.
 
 I searched the docs, but can't remember, if and how I have to 
 assign the externals  or the path of the externals to my stack or 
 even why LC doesn't loads my externals anymore, though I haven't 
 changed anything on this stack since last year, where everything 
 worked fine
>> until the last use.
 
 
 
 Can anyone shed some light on the handling of externals for me, 
 what could have happened here?
 
 Thank you
 
 Tiemo
 
 
 
 
 
 ___
 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,