Re: Windows 64-bit builds

[J. Landman Gay via use-livecode]

Oops, I had a brain freeze. I don't see the option in Windows either, 
it's in the Mac settings in LC 8.1. Now that you've drawn my attention 
to it, I see it's reversed in LC 9.0.2 which says that 32-bit is 
deprecated. So, no problem.


Thanks for the correction. I need more sleep.

On 1/27/19 3:44 PM, Matthias Rebbe via use-livecode wrote:

Am very interested in 64bit Windows standalones, but cannot see that option in 
Standalone Settings in my LC 9.0.2 on Mac OS X.
In what LC version do you see that option?

Btw, when the Mac OS X 64-bit option was still experimental i used it a lot and 
did not run into any problem with my apps.


Matthias Rebbe

free tools for Livecoders:
https://instamaker.dermattes.de 
https://winsignhelper.dermattes.de 


Am 27.01.2019 um 22:27 schrieb J. Landman Gay via use-livecode 
mailto:use-livecode@lists.runrev.com>>:

Standalone settings shows the Windows 64-bit option as "experimental." How 
experimental is it, and has anyone had any issues?

A little story: I was just contacted by a client I did some work for 15 years 
ago. She's been running the same app all this time, but a while back she lost 
the ability to run it on her OS X Mac at home (the app was built for OS 9) so 
she wants it updated for OS X. The ancient Windows app still runs on her 
Windows 10 box at work.

Since I'm going to rebuild it for OS X, we're going to update the Windows 
version as well. I'm wondering if I should go ahead and use 64-bit for that to 
ensure the app will still work 15 years into the future.

It's astounding to me that a LiveCode app built with MC 2.7 is still viable in 
today's software environment. You have to applaud the team's incredible 
dedication to backward compatibility.

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

[hh via use-livecode]

I don't know exactly the differences between the editions.
But did you already try https://livecode.com/trial/ ?

___
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: IndyCam2_v100

[David Bovill via use-livecode]

Would be great to have a better description so I can see what it looks
like, and what it does? For instance i don't need or want snapshot
functionality - and I'm scared to fork out $500 for Indy - blind as i've no
real idea what is in there.

After all i just spend $80 or thereabouts on Community Plus because the
description made me think I'd have some sort of access to the commercial
plugins - only to find that is not the case. Surely this is a bad idea -
shouldn't we get some time to see if we want to buy?

On Sun, 27 Jan 2019 at 22:09, hh via use-livecode <
use-livecode@lists.runrev.com> wrote:

> This is now updated to v102 that removes a display bug on Windows
> where I could not make two cams visible at the same time. So, if
> you have two cameras attached then you see on MacOS the display
> of both and on Windows10 only the selected one.
>
> Tested to work on MacOS 10.14 and Windows 10 with LC 9.0.2 Indy.
>
> > hh wrote:
> > *** The stack does NOT run with LC Community ***
> > (Because it uses the cameraControl that is available in
> > the Indy or Business versions of LC only.)
> >
> > Download IndyCam2 from "Sample stacks" or
> > http://livecodeshare.runrev.com/stack/927/
> >
> > You can take snapshots with up to two (intern oder extern)
> > cameras, may be also simple webcams.
> > Each snapshot has at about 240 KByte.
> >
> > The snapshots can be filtered (directly in the stack) with
> > one of the image effects from LCImageToolBox_89.
> >
> > There is also a timer for using this as timelapseCamera,
> > shooting in intervals of 1 to 36600 seconds. While such a
> > timelapse is running you can change the camera, the image
> > filter and the interval.
> >
> > There is help in the stack.
>
>
> ___
> 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: Never, ever use the name of a built-in property as a custom property

[David Bovill via use-livecode]

Yes. I'm scared as well about naming things :) I'm not sure what is safe.
Thee is a tension between making your code readable, and worrying that your
use of a natural language term will clash with some evolution of the
language that may later get added as a native feature. Is nothing safe?

On Sun, 27 Jan 2019 at 17:01, Geoff Canyon via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Sure, I'm not arguing for custom property sets -- just saying that if you
> *are* going to use them, don't bork the naming convention.
> ___
> 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: IndyCam2_v100

[hh via use-livecode]

This is now updated to v102 that removes a display bug on Windows
where I could not make two cams visible at the same time. So, if
you have two cameras attached then you see on MacOS the display
of both and on Windows10 only the selected one.

Tested to work on MacOS 10.14 and Windows 10 with LC 9.0.2 Indy.

> hh wrote:
> *** The stack does NOT run with LC Community ***
> (Because it uses the cameraControl that is available in
> the Indy or Business versions of LC only.)
> 
> Download IndyCam2 from "Sample stacks" or
> http://livecodeshare.runrev.com/stack/927/
> 
> You can take snapshots with up to two (intern oder extern)
> cameras, may be also simple webcams.
> Each snapshot has at about 240 KByte.
> 
> The snapshots can be filtered (directly in the stack) with
> one of the image effects from LCImageToolBox_89.
> 
> There is also a timer for using this as timelapseCamera,
> shooting in intervals of 1 to 36600 seconds. While such a
> timelapse is running you can change the camera, the image
> filter and the interval.
> 
> There is help in the stack.


___
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: Windows 64-bit builds

[Matthias Rebbe via use-livecode]

Am very interested in 64bit Windows standalones, but cannot see that option in 
Standalone Settings in my LC 9.0.2 on Mac OS X.
In what LC version do you see that option?

Btw, when the Mac OS X 64-bit option was still experimental i used it a lot and 
did not run into any problem with my apps.


Matthias Rebbe

free tools for Livecoders:
https://instamaker.dermattes.de 
https://winsignhelper.dermattes.de 

> Am 27.01.2019 um 22:27 schrieb J. Landman Gay via use-livecode 
> mailto:use-livecode@lists.runrev.com>>:
> 
> Standalone settings shows the Windows 64-bit option as "experimental." How 
> experimental is it, and has anyone had any issues?
> 
> A little story: I was just contacted by a client I did some work for 15 years 
> ago. She's been running the same app all this time, but a while back she lost 
> the ability to run it on her OS X Mac at home (the app was built for OS 9) so 
> she wants it updated for OS X. The ancient Windows app still runs on her 
> Windows 10 box at work.
> 
> Since I'm going to rebuild it for OS X, we're going to update the Windows 
> version as well. I'm wondering if I should go ahead and use 64-bit for that 
> to ensure the app will still work 15 years into the future.
> 
> It's astounding to me that a LiveCode app built with MC 2.7 is still viable 
> in today's software environment. You have to applaud the team's incredible 
> dedication to backward compatibility.
> 
> -- 
> 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

Windows 64-bit builds

[J. Landman Gay via use-livecode]

Standalone settings shows the Windows 64-bit option as "experimental." 
How experimental is it, and has anyone had any issues?


A little story: I was just contacted by a client I did some work for 15 
years ago. She's been running the same app all this time, but a while 
back she lost the ability to run it on her OS X Mac at home (the app was 
built for OS 9) so she wants it updated for OS X. The ancient Windows 
app still runs on her Windows 10 box at work.


Since I'm going to rebuild it for OS X, we're going to update the 
Windows version as well. I'm wondering if I should go ahead and use 
64-bit for that to ensure the app will still work 15 years into the future.


It's astounding to me that a LiveCode app built with MC 2.7 is still 
viable in today's software environment. You have to applaud the team's 
incredible dedication to backward compatibility.


--
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: Trying to get Camera Control. Community Plus License

[Richmond via use-livecode]

I've just been fiddling around with the "Video Capture.rev" stack
from LC 4.5 with no joy in LC 8.1.10.

Richmond.

On 27.01.19 17:02, hh via use-livecode wrote:

Find some info here:
https://livecode.com/products/livecode-platform/pricing/

 From the 9.0.2-dict entry to cameraControlCreate:
Edition: Indy
OS: mac, windows, ios, android

So, the Community plus edition is not the Indy edition.

I will soon publish a *timelapseCamera* stack that runs on
Mac/Win/linux with LC 6/7/8/9 and Raspi (LC 651/704)
for ALL editions of LC.
___
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: Never, ever use the name of a built-in property as a custom property

[Geoff Canyon via use-livecode]

Sure, I'm not arguing for custom property sets -- just saying that if you
*are* going to use them, don't bork the naming convention.
___
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: Trying to get Camera Control. Community Plus License

[hh via use-livecode]

Find some info here:
https://livecode.com/products/livecode-platform/pricing/

>From the 9.0.2-dict entry to cameraControlCreate:
Edition: Indy
OS: mac, windows, ios, android

So, the Community plus edition is not the Indy edition.

I will soon publish a *timelapseCamera* stack that runs on
Mac/Win/linux with LC 6/7/8/9 and Raspi (LC 651/704)
for ALL editions of LC.
___
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

Trying to get Camera Control. Community Plus License

[David Bovill via use-livecode]

Not sure did i get the wrong license?

>From the Livecode web site:

Just like LiveCode Community this is an open source edition of LIveCode and
> carries with it the same requirement for making your code open and
> shareable. Where it differs from the Open Source edition is in all of the
> extra goodies it comes with. *You can access all the commercial
> extensions in the LiveCode store*, learn the language faster with
> autocomplete inside the script editor


But no Camera Control. In fact I can't find any way to see what extensions
are available or bundled with the various platforms - so how does it work?
___
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: Never, ever use the name of a built-in property as a custom property

[David Bovill via use-livecode]

Hi Geoff, for me the solution is to have a naming convention for all of a
developers / projects work - so everything is prefixed by 4 letters, and
then in the case of custom properties / custom property sets - to migrate
off them and just stick to arrays. The custom property / set syntax was
always confusing, and since we've had arrays there is as far as I can tell
no advantage in using them over simply storing the data you want as an
array in a custom property.

I guess you could combine the two approaches and use a top-level set? But
for me the simplicity of cutting down on that level of architecture and
just using well named custom properties with arrays stored in them has the
advantage that you can refer to them directly in script without any library
to make the job easier?


On Sat, 26 Jan 2019 at 21:34, Geoff Canyon via use-livecode <
use-livecode@lists.runrev.com> wrote:

> https://github.com/gcanyon/navigator/issues/27
>
> I just found that Navigator breaks when editing the custom properties of
> datagrids, because of the custom property dgProps["style"]. When I
> originally added custom properties to the property editor in Navigator it
> was simple: I pretty much had to add one line here and there, and I was
> done. Namely:
>
>   if the cCustomProperties of me is true
>   then set the customPropertySet of tID to (the cCustomPropertySet of
> me)
>
> And then set the properties as usual. So easy. But setting the property
> breaks if the custom property is "style", with the error that the object
> doesn't have that property.
>
> So now I'm spending time going through Navigator and replacing the above
> with code like this:
>
>  put value(merge("the [[pCustomPropertySet]][
> [[quote]][[P]][[quote]]] of [[pID]]")) into pIDP
>
> (if anyone has a cleaner solution, I'd love to hear it)
>
> So: use unique names for your custom properties. Prefix them all with a "u"
> as some people do, for example.
>
> Or don't. Navigator's next update will accommodate you anyway.
>
> 
> ___
> 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: Navigator 7.2rc1 is available

[Geoff Canyon via use-livecode]

7.2.1rc1 is available

There is now a checkbox in the prefs to fold dataGrids by default. Also, I
fixed the custom property editor to work even if custom properties have the
same name as built-in properties, updated the display of folded controls,
and updated Navigator's property editor to do a soft display update when
setting values, so changing the name of controls will be reflected when the
editor is closed.

Fixes:
https://github.com/gcanyon/navigator/issues/27
https://github.com/gcanyon/navigator/issues/26
https://github.com/gcanyon/navigator/issues/24

Updates:
https://github.com/gcanyon/navigator/issues/19

On Fri, Jan 25, 2019 at 9:13 PM Geoff Canyon  wrote:

> The fold control bar uses this stack as its behavior: stack
> "rev_g_groupFoldBar"
>
> That script is:
>
> on mouseUp
>put getID(barClickLine()) into CL
>if the number of lines of CL > 1 or word 1 of CL is not "group" then
> exit mouseUp
>setFolded CL
>doUpdateDisplay true
> end mouseUp
>
> So it's pretty much down to three things:
>
> 1.a. Does barClickLine() return the proper line?
> 1.b. Does getID() return the right ID? And is it the long ID?
> 2. Does setFolded work?
> 3. Does doUpdateDisplay do something to reset the folds before displaying?
> (This is what was wrong the last time).
>
> One thing to try would be this:
>
> dispatch "setFolded" to stack "revNavigator" with (the long id of  group navigator is displaying>),true
>
> Navigator won't immediately update its display, but clicking in
> Navigator's list or selecting Update List Now on the Action menu should do
> it, and then that group should be displayed folded. I just did this and it
> worked for me. If this works for you then we've narrowed the problem down
> to 1. If it doesn't work, then 2 or 3.
>
> gc
>
> On Fri, Jan 25, 2019 at 3:11 PM Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Nope. Running LC 9.0.2 Community, MacOS 10.14.2, Navigator 7.2 RC1. If
>> you point me to where the folding code actually happens, I can turn on rev
>> development and trace it.
>>
>> Bob S
>>
>>
>> > On Jan 25, 2019, at 14:16 , Geoff Canyon via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> >
>> > I'm not seeing this? I tried both with a specific stack and (what I
>> > remember from the last time) "this card of the topstack". Folding is
>> > working for me, both by clicking in the margin, and by selecting a fold
>> > level on the popup menu for a card or group.
>> >
>> > Any specific recipe?
>> >
>> > gc
>>
>>
>> ___
>> 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