Re: Refactoring is your friend / moving from 6.x to 9.x

[Kay C Lan via use-livecode]

On Mon, Dec 31, 2018 at 9:17 AM Mark Wieder via use-livecode
 wrote:
>
> Yes, it is definitely a change in behavior.
I want to strongly disagree with your conclusion here ;-)
>
> This isn't the only place where the dictionary is wrong.

My 9.0.2 Dictionary quite clearly states for the property 'lockScreen'
that it was introduced and hasn't changed since version 1.0.  Which
means, as Craig said, it's exactly the same as it was in HC. The
Dictionary also clearly states:

"LiveCode keeps count of how many times the screen has been locked.
You must balance each unlock with a lock; if you lock the screen twice
and then unlock it once, the screen remains locked."

Yes it is unfortunate that that important statement doesn't appear in
the other relevant lock screen and unlock screen entries.

I'm with Herman, learnt a long long time ago to use a simple if
statement to keep the lockScreen count to 1.

___
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

DataView and DataView Tree Levure Helpers

[Trevor DeVore via use-livecode]

Hi folks,

Over the holiday break I took time to package up some UI controls I use in
my own projects and make them available as helpers for Levure apps*. The
controls are named "DataView" and "DataView Tree". The DataView is a
leaner, more efficient DataGrid Form. It allows you to efficiently display
highly customized rows of data on desktop and mobile. The DataGrid Tree is
built on top of the DataView and works with a tree structure.

I've prepared a demo project with examples of each type of control. Here
are the github repos for the demo project and the controls themselves.

Demo Github repo: https://github.com/trevordevore/dataview_demo
DataView Github repo: https://github.com/trevordevore/levurehelper-dataview
DataView Tree Github repo:
https://github.com/trevordevore/levurehelper-dataview_tree

I have also posted a video which walks through the demo project:

https://youtu.be/euIHj1Qrokk

While there is still work to do on the documentation, the demo stack can
help the motivated developer start using the controls in their own projects.

* Of course the code will work in apps that don't use the Levure framework.
You just need to integrate all of the stacks and scripts into your app
manually.

-- 
Trevor DeVore
ScreenSteps
www.screensteps.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: Navigator 7.0.1rc1 is available -- Multi-target windows!

[Geoff Canyon via use-livecode]

Glad to help. Let me know if there's anything still missing.

On Wed, Jan 2, 2019 at 2:53 PM hh via use-livecode <
use-livecode@lists.runrev.com> wrote:

> This is (not only now) a real comfortable developer tool.
> Especially when starting a project the new features are very effective.
> Thanks for that!
>
>
> ___
> 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.0.1rc1 is available -- Multi-target windows!

[Geoff Canyon via use-livecode]

On Wed, Jan 2, 2019 at 5:04 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 1/2/19 2:30 PM, Geoff Canyon via use-livecode wrote:
> > Ha, I knew that to a select subset of people this would be the most
> > important feature of the update :-)
>
> Heh. Yeah, I've backburned for now a talk entitled "Global Variables and
> Their Discontents"
>

The last remaining global variable in Navigator is on my short list for
removal. It will be easy relative to the others that are already gone, it
just wasn't critical to the current update, and I didn't realize it was the
last one until last night.
___
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.0.1rc1 is available -- Multi-target windows!

[Mark Wieder via use-livecode]

On 1/2/19 2:30 PM, Geoff Canyon via use-livecode wrote:

Ha, I knew that to a select subset of people this would be the most
important feature of the update :-)


Heh. Yeah, I've backburned for now a talk entitled "Global Variables and 
Their Discontents"


--
 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: Whoops: Getting the name of the script only stack an handler is in

[William Prothero via use-livecode]

Bob:
I tried it. Yes:
put the name of me  —returns the name of the control that hosts the behavior 
script
put the name of this me —returns the name of the behavior script

Best,
Bill

> On Jan 2, 2019, at 11:34 AM, Bob Sneidar via use-livecode 
>  wrote:
> 
> Ah yes then, me refers to the object the script belongs to. With behaviors, 
> me refers to the *instance* of the script which is "owned" by the object 
> being interacted with. "this me" refers to the actual behavior script. What 
> you want is "this me". 
> 
> Bob S
> 
> 
>> On Jan 2, 2019, at 08:35 , prothero--- via use-livecode 
>>  wrote:
>> 
>> Bob,
>> Thanks for the response. You are probably right, the filename of me should 
>> work. I don’t know whether it’s old age or not, but several times I have 
>> worked on a problem until I felt I had exhausted my ideas, posted a question 
>> to this list, then a solution immediately came to mind. If this happens, I 
>> will post an update with apologies. 
>> 
>> In the case you responded to, I was trying to find the name of the script 
>> only stack that contained the currently running handler. 
>> 
>> Put me into thisStack  —works fine
>> the short name of this stack —wrong, gives the name of the calling stack, in 
>> my case, anyway.
>> put the short name of the target —not it
>> 
>> “The target” is great for determining the control that initiated the script, 
>> but it does lose its original value when a “send in time” command is given, 
>> like commonly done during an animation.
>> 
>> Anyway, Bob, thanks for your response. 
>> 
>> William Prothero
>> http://es.earthednet.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: Navigator 7.0.1rc1 is available -- Multi-target windows!

[hh via use-livecode]

This is (not only now) a real comfortable developer tool.
Especially when starting a project the new features are very effective.
Thanks for that!


___
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.0.1rc1 is available -- Multi-target windows!

[Geoff Canyon via use-livecode]

Ha, I knew that to a select subset of people this would be the most
important feature of the update :-)

On Wed, Jan 2, 2019 at 2:28 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 1/2/19 2:25 PM, Geoff Canyon via use-livecode wrote:
> > I also got rid of all but one of the global variables Navigator has used
> > since the very first version.
>
> Yay!
>
> --
>   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: Navigator 7.0.1rc1 is available -- Multi-target windows!

[Geoff Canyon via use-livecode]

I forgot -- I made a video illustrating how the new features work. Here it
is: https://www.youtube.com/watch?v=B1_avMJnZ6k

On Wed, Jan 2, 2019 at 2:25 PM Geoff Canyon  wrote:

> I also got rid of all but one of the global variables Navigator has used
> since the very first version. I had tried in the past to do away with them,
> and failed miserably. But now they are vanquished!
>
> On Wed, Jan 2, 2019 at 2:17 PM Geoff Canyon  wrote:
>
>> As usual, you can get Navigator here
>> . Or grab
>> it from GitHub .
>>
>> Navigator now supports multiple targets per window. You can still have as
>> many Navigator windows as you like, but now each window can display the
>> controls for any set of cards and groups.
>>
>> Select multiple stacks in the stack list, then right-click and select
>> browse controls, and Navigator will display all of the stacks in the same
>> list.
>>
>> In any display, select any combination of cards and groups. Right-click
>> and select browse controls, and Navigator will display all of the
>> containers in the same list.
>>
>> In any command that sets the target for Navigator, hold down the Shift
>> key to add to the target list instead of replacing it.
>>
>> To remove a container from the list, right-click the container and select
>> Stop Browsing from the popup menu. Navigator will remove the container from
>> the display while retaining the others in the list.
>>
>> Creating Navigator 7 required completely reworking how Navigator relayers
>> controls, which resulted in several improvements. First, if you drag a
>> control beneath a group, Navigator is now able to relayer the control
>> properly, without forcing it into the group. You can still drag controls
>> into and out of groups. And if you drag a grouped control to the bottom of
>> the group, it will remain in the group.
>>
>> The new relayering code is smart about whether to move or duplicate
>> controls. Even if there are two representations of a container in the list,
>> dragging a control from one to the other will simply relayer the control
>> without duplicating it. Of course dragging a control from one container to
>> another will duplicate it.
>>
>> Holding the option key reverses this behavior: if you hold the option key
>> while dragging a control within its container, the control will be
>> duplicated. And if you hold the option key while dragging a control to a
>> different container, the control will be moved to the new location, and
>> removed from the original.
>>
>> I also updated the target crosshair so selecting an IDE stack will only
>> work if "Show IDE Stacks" is selected in the target menu.
>>
>> I look forward to your feedback!
>>
>
___
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.0.1rc1 is available -- Multi-target windows!

[Mark Wieder via use-livecode]

On 1/2/19 2:25 PM, Geoff Canyon via use-livecode wrote:

I also got rid of all but one of the global variables Navigator has used
since the very first version.


Yay!

--
 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: Whoops: Getting the name of the script only stack an handler is in

[Mark Wieder via use-livecode]

On 1/2/19 8:01 AM, Bob Sneidar via use-livecode wrote:

And I replied before checking all my other emails. Seriously, at some point we 
need to develop a list system where emails remain threaded. I have over 40 from 
this list this morning, and reading through every one, then trying to go back 
and respond is a little more brainwork than I am used to before my 3rd cup of 
coffee. :-)


Whoa! There are email clients that don't support threading?
Here ya go:

https://www.thunderbird.net/en-US/

--
 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: Navigator 7.0.1rc1 is available -- Multi-target windows!

[Geoff Canyon via use-livecode]

I also got rid of all but one of the global variables Navigator has used
since the very first version. I had tried in the past to do away with them,
and failed miserably. But now they are vanquished!

On Wed, Jan 2, 2019 at 2:17 PM Geoff Canyon  wrote:

> As usual, you can get Navigator here
> . Or grab
> it from GitHub .
>
> Navigator now supports multiple targets per window. You can still have as
> many Navigator windows as you like, but now each window can display the
> controls for any set of cards and groups.
>
> Select multiple stacks in the stack list, then right-click and select
> browse controls, and Navigator will display all of the stacks in the same
> list.
>
> In any display, select any combination of cards and groups. Right-click
> and select browse controls, and Navigator will display all of the
> containers in the same list.
>
> In any command that sets the target for Navigator, hold down the Shift key
> to add to the target list instead of replacing it.
>
> To remove a container from the list, right-click the container and select
> Stop Browsing from the popup menu. Navigator will remove the container from
> the display while retaining the others in the list.
>
> Creating Navigator 7 required completely reworking how Navigator relayers
> controls, which resulted in several improvements. First, if you drag a
> control beneath a group, Navigator is now able to relayer the control
> properly, without forcing it into the group. You can still drag controls
> into and out of groups. And if you drag a grouped control to the bottom of
> the group, it will remain in the group.
>
> The new relayering code is smart about whether to move or duplicate
> controls. Even if there are two representations of a container in the list,
> dragging a control from one to the other will simply relayer the control
> without duplicating it. Of course dragging a control from one container to
> another will duplicate it.
>
> Holding the option key reverses this behavior: if you hold the option key
> while dragging a control within its container, the control will be
> duplicated. And if you hold the option key while dragging a control to a
> different container, the control will be moved to the new location, and
> removed from the original.
>
> I also updated the target crosshair so selecting an IDE stack will only
> work if "Show IDE Stacks" is selected in the target menu.
>
> I look forward to your feedback!
>
___
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

Navigator 7.0.1rc1 is available -- Multi-target windows!

[Geoff Canyon via use-livecode]

As usual, you can get Navigator here
. Or grab it
from GitHub .

Navigator now supports multiple targets per window. You can still have as
many Navigator windows as you like, but now each window can display the
controls for any set of cards and groups.

Select multiple stacks in the stack list, then right-click and select
browse controls, and Navigator will display all of the stacks in the same
list.

In any display, select any combination of cards and groups. Right-click and
select browse controls, and Navigator will display all of the containers in
the same list.

In any command that sets the target for Navigator, hold down the Shift key
to add to the target list instead of replacing it.

To remove a container from the list, right-click the container and select
Stop Browsing from the popup menu. Navigator will remove the container from
the display while retaining the others in the list.

Creating Navigator 7 required completely reworking how Navigator relayers
controls, which resulted in several improvements. First, if you drag a
control beneath a group, Navigator is now able to relayer the control
properly, without forcing it into the group. You can still drag controls
into and out of groups. And if you drag a grouped control to the bottom of
the group, it will remain in the group.

The new relayering code is smart about whether to move or duplicate
controls. Even if there are two representations of a container in the list,
dragging a control from one to the other will simply relayer the control
without duplicating it. Of course dragging a control from one container to
another will duplicate it.

Holding the option key reverses this behavior: if you hold the option key
while dragging a control within its container, the control will be
duplicated. And if you hold the option key while dragging a control to a
different container, the control will be moved to the new location, and
removed from the original.

I also updated the target crosshair so selecting an IDE stack will only
work if "Show IDE Stacks" is selected in the target menu.

I look forward to your feedback!
___
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: Livecode Server GoDaddy

[Keith Clarke via use-livecode]

It’s a few months ago now and I’m no linux expert so not good with logs, etc. 
Maybe the first check is whether the hosting is CentOS 6 or 7? 

When I hit these issues, I started a thread on this list “LiveCode Server on 
CentOS 6?” on 28 July, 2018. Warren Samples kindly confirmed that glibc 2.13+ 
was required for LC 8 & 9, he had LC Server running on CentOS 7 and CentOS 
ships with glibc 2.12, which is too old.

Apparently the command ldd --version might reveal what’s running.

Best,
Keith

> On 2 Jan 2019, at 20:24, Ralph DiMola via use-livecode 
>  wrote:
> 
> Where did you see that error? The error log is empty.
> 
> That's very depressing. I sold this based on the info I got from the GoDaddy
> sales team before I signed up.
> 
> 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 Keith Clarke via use-livecode
> Sent: Wednesday, January 02, 2019 2:48 PM
> To: How to use LiveCode
> Cc: Keith Clarke
> Subject: Re: Livecode Server GoDaddy
> 
> Ralph, I gave up on getting LCS running on a GoDaddy VPS back in the summer
> as it was too old at CentOS 6 with dependencies on glibc failing - I was
> getting 500 errors IIRC.
> 
> Good luck!
> 
> Keith
> 
>> On 2 Jan 2019, at 19:42, Ralph DiMola via use-livecode
>  wrote:
>> 
>> I keep getting 500 errors. I changed the htacces file to point .lc 
>> files to the livecode server executable. Log files have no useful 
>> info. The error log has nothing.
>> Has anyone gotten LC Server working on GoDaddy shared hosting?
>> 
>> Thanks
>> 
>> Ralph DiMola
>> IT Director
>> Evergreen Information Services
>> rdim...@evergreeninfo.net
>> 
>> 
>> ___
>> 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


___
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: Livecode Server GoDaddy

[Ralph DiMola via use-livecode]

Where did you see that error? The error log is empty.

That's very depressing. I sold this based on the info I got from the GoDaddy
sales team before I signed up.

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 Keith Clarke via use-livecode
Sent: Wednesday, January 02, 2019 2:48 PM
To: How to use LiveCode
Cc: Keith Clarke
Subject: Re: Livecode Server GoDaddy

Ralph, I gave up on getting LCS running on a GoDaddy VPS back in the summer
as it was too old at CentOS 6 with dependencies on glibc failing - I was
getting 500 errors IIRC.

Good luck!

Keith

> On 2 Jan 2019, at 19:42, Ralph DiMola via use-livecode
 wrote:
> 
> I keep getting 500 errors. I changed the htacces file to point .lc 
> files to the livecode server executable. Log files have no useful 
> info. The error log has nothing.
> Has anyone gotten LC Server working on GoDaddy shared hosting?
> 
> Thanks
> 
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
> 
> 
> ___
> 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: Livecode Server GoDaddy

[Keith Clarke via use-livecode]

Ralph, I gave up on getting LCS running on a GoDaddy VPS back in the summer as 
it was too old at CentOS 6 with dependencies on glibc failing - I was getting 
500 errors IIRC.

Good luck!

Keith

> On 2 Jan 2019, at 19:42, Ralph DiMola via use-livecode 
>  wrote:
> 
> I keep getting 500 errors. I changed the htacces file to point .lc files to
> the livecode server executable. Log files have no useful info. The error log
> has nothing.
> Has anyone gotten LC Server working on GoDaddy shared hosting?
> 
> Thanks
> 
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
> 
> 
> ___
> 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

Livecode Server GoDaddy

[Ralph DiMola via use-livecode]

I keep getting 500 errors. I changed the htacces file to point .lc files to
the livecode server executable. Log files have no useful info. The error log
has nothing.
Has anyone gotten LC Server working on GoDaddy shared hosting?

Thanks

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


___
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: Whoops: Getting the name of the script only stack an handler is in

[Bob Sneidar via use-livecode]

Ah yes then, me refers to the object the script belongs to. With behaviors, me 
refers to the *instance* of the script which is "owned" by the object being 
interacted with. "this me" refers to the actual behavior script. What you want 
is "this me". 

Bob S


> On Jan 2, 2019, at 08:35 , prothero--- via use-livecode 
>  wrote:
> 
> Bob,
> Thanks for the response. You are probably right, the filename of me should 
> work. I don’t know whether it’s old age or not, but several times I have 
> worked on a problem until I felt I had exhausted my ideas, posted a question 
> to this list, then a solution immediately came to mind. If this happens, I 
> will post an update with apologies. 
> 
> In the case you responded to, I was trying to find the name of the script 
> only stack that contained the currently running handler. 
> 
> Put me into thisStack  —works fine
> the short name of this stack —wrong, gives the name of the calling stack, in 
> my case, anyway.
> put the short name of the target —not it
> 
> “The target” is great for determining the control that initiated the script, 
> but it does lose its original value when a “send in time” command is given, 
> like commonly done during an animation.
> 
> Anyway, Bob, thanks for your response. 
> 
> William Prothero
> http://es.earthednet.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

Re: LiveCode 9.0.2 on Windows unable to build for Mac?!?!?!?

[Paul Dupuis via use-livecode]

Bug report submitted to LiveCode: 
https://quality.livecode.com/show_bug.cgi?id=21772


___
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: Whoops: Getting the name of the script only stack an handler is in

[prothero--- via use-livecode]

Bob,
Thanks for the response. You are probably right, the filename of me should 
work. I don’t know whether it’s old age or not, but several times I have worked 
on a problem until I felt I had exhausted my ideas, posted a question to this 
list, then a solution immediately came to mind. If this happens, I will post an 
update with apologies. 

In the case you responded to, I was trying to find the name of the script only 
stack that contained the currently running handler. 

 Put me into thisStack  —works fine
the short name of this stack —wrong, gives the name of the calling stack, in my 
case, anyway.
put the short name of the target —not it

“The target” is great for determining the control that initiated the script, 
but it does lose its original value when a “send in time” command is given, 
like commonly done during an animation.

Anyway, Bob, thanks for your response. 

William Prothero
http://es.earthednet.org

> On Jan 2, 2019, at 8:03 AM, Bob Sneidar via use-livecode 
>  wrote:
> 
> Doesn't "the filename of me" work? 
> 
> Bob S
> 
> 
>> On Dec 31, 2018, at 14:48 , William Prothero via use-livecode 
>>  wrote:
>> 
>> My question:
>> How do I get the name of the script only stack that holds the “Feature” 
>> code? The above code gives me the name of the main stack, which is not 
>> useful for my purposes.
>> 
>> Best,
>> Bill
> 
> ___
> 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: Refactoring is your friend / moving from 6.x to 9.x

[J. Landman Gay via use-livecode]

I first saw this loop in a script by Brett Sher, who called it
"unlockReally", so you're close. :)

(I accidentally put this response in the wrong thread at first where it 
doesn't make any sense, sorry about that.)

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On January 2, 2019 5:26:11 AM Andre Garzia via use-livecode 
 wrote:



That loop is briliant. I am tempted to place it into a command called
"unlockScreenForReal"

On Mon, Dec 31, 2018, 16:38 dunbarxx via use-livecode <
use-livecode@lists.runrev.com wrote:


Not sure if this is still relevant in LC, but in HC, lock screen commands
were queued. So the fix, so that one did not have to count the number of
locks through perhaps several handlers, was:

repeat until the lockScreen is false
unlock screen
end repeat

Craig



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

___
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: Refactoring is your friend / moving from 6.x to 9.x

[J. Landman Gay via use-livecode]

I first saw this loop in a script by Brett Sher, who called it 
"unlockReally", so you're close. :)

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On January 2, 2019 5:26:09 AM Andre Garzia via use-livecode 
 wrote:



That loop is briliant. I am tempted to place it into a command called
"unlockScreenForReal"

On Mon, Dec 31, 2018, 16:38 dunbarxx via use-livecode <
use-livecode@lists.runrev.com wrote:


Not sure if this is still relevant in LC, but in HC, lock screen commands
were queued. So the fix, so that one did not have to count the number of
locks through perhaps several handlers, was:

repeat until the lockScreen is false
unlock screen
end repeat

Craig



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

___
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: Video-Fun2

[Bob Sneidar via use-livecode]

CHEESE!

Bob S


> On Jan 1, 2019, at 10:07 , Richmond via use-livecode 
>  wrote:
> 
> If, however, you were to promote an automated bottom-washer
> that played Donald Trump's "March on Moscow" you'd get so much money
> you would know what to do with it.
> 
> Richmond.


___
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: Refactoring is your friend / moving from 6.x to 9.x

[Bob Sneidar via use-livecode]

only sqLite. 

Bob S


> On Dec 31, 2018, at 13:32 , J. Landman Gay via use-livecode 
>  wrote:
> 
> I'm generally deficient when it comes to databases but curious how one 
> creates a memory based one. Is there a trick, and does it work with others 
> besides sql?
> 
> This is probably a newbie question.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On December 31, 2018 11:31:15 AM Bob Sneidar via use-livecode 
>  wrote:
> 
> 


___
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: Refactoring is your friend / moving from 6.x to 9.x

[Bob Sneidar via use-livecode]

put revOpenDatabase("sqlite",":memory:") into tDBID

Bob S


> On Dec 31, 2018, at 13:32 , J. Landman Gay via use-livecode 
>  wrote:
> 
> I'm generally deficient when it comes to databases but curious how one 
> creates a memory based one. Is there a trick, and does it work with others 
> besides sql?
> 
> This is probably a newbie question.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On December 31, 2018 11:31:15 AM Bob Sneidar via use-livecode 
>  wrote:
> 
> 


___
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: Refactoring is your friend / moving from 6.x to 9.x

[Bob Sneidar via use-livecode]

What if you accidentally use the wrong name reference, then want to change it? 

Bob S


> On Dec 31, 2018, at 10:38 , Geoff Canyon via use-livecode 
>  wrote:
> 
>> I wish we had better refactoring tools
>> so that we could rename a handler and all code that called that handler
>> was fixed, or stuff such as rename variable...
>> 
> 
> One of the reasons I like experimenting with different environments is to
> see what advantages they have. One advantage that FileMaker Pro has had for
> 25 years, is that all references to tables, fields, and layouts, are based
> on underlying unique IDs. Meaning that if you rename something, the
> underlying reference ID doesn't change, and anywhere the reference occurs,
> the name change is reflected automatically. Obviously this would require
> significant effort to work in any text-file-based system, but it has always
> amazed me that I have never seen this feature replicated elsewhere.


___
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: Whoops: Getting the name of the script only stack an handler is in

[Bob Sneidar via use-livecode]

Doesn't "the filename of me" work? 

Bob S


> On Dec 31, 2018, at 14:48 , William Prothero via use-livecode 
>  wrote:
> 
> My question:
> How do I get the name of the script only stack that holds the “Feature” code? 
> The above code gives me the name of the main stack, which is not useful for 
> my purposes.
> 
> Best,
> Bill

___
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: Whoops: Getting the name of the script only stack an handler is in

[Bob Sneidar via use-livecode]

And I replied before checking all my other emails. Seriously, at some point we 
need to develop a list system where emails remain threaded. I have over 40 from 
this list this morning, and reading through every one, then trying to go back 
and respond is a little more brainwork than I am used to before my 3rd cup of 
coffee. :-)

Bob S


> On Dec 31, 2018, at 14:48 , William Prothero via use-livecode 
>  wrote:
> 
> Folks:
> Sorry, I accidentally sent the email before finishing it. Here’s the complete 
> message.
> But perhaps I’ve solved it. I only need to put the name of the “feature” 
> stack in the pollActions handler. Anyway, I still have my question.
> 
> I’m trying to implement a structure where I can simply add script only stacks 
> that seamlessly add capability to my app. To do this, I have all of the 
> “feature” stacks in a given folder, and when I initialize the app, I start 
> using all of the “feature” stacks. Then I want to initialize all of them, so 
> I send a message that gets passed in each “feature” stack.
> 
> I do, in each “feature” stack (which doesn’t give me the answer I want):
> 
> on pollActions
>   put the short name of the current stack into myAction  (I want the name 
> of the stack that contains this script)
>   dispatch "actionsList" to cd "Opening" of stack "CP_Main" with myAction
>   pass pollActions
> end pollActions
> 
> 
> In the main stack, I have:
> 
> local actionsList
> 
> on actionsList tList
>   put tList after actionsList
> end actionsList
> 
> 
> 
> My question:
> How do I get the name of the script only stack that holds the “Feature” code? 
> The above code gives me the name of the main stack, which is not useful for 
> my purposes.
> 
> Best,
> Bill

___
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: Getting the name of the script only stack an handler is in

[Bob Sneidar via use-livecode]

I don't mean to sound flippant, but what is the question?

Bob S


> On Dec 31, 2018, at 14:38 , William Prothero via use-livecode 
>  wrote:
> 
> Folks:
> I’m trying to implement a structure where I can simply add script only stacks 
> that seamlessly add capability to my app. To do this, I have all of the 
> “feature” stacks in a given folder, and when I initialize the app, I start 
> using all of the “feature” stacks. Then I want to initialize all of them, so 
> I send a message that gets passed in each “feature” stack.
> 
> I do, in each “feature” stack:
> on pollActions
> 
>   put the short name of the current stack into myAction
> 
>   dispatch "actionsList" to cd "Opening" of stack "CP_Main" with myAction
> 
>   pass pollActions
> 
> end pollActions

___
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: Refactoring is your friend / moving from 6.x to 9.x

[Ali Lloyd via use-livecode]

> Is there a way to "safely" add to LC contextual menu in the script editor?

Yes! It is in a script-only stack behavior of the editor field:
https://github.com/livecode/livecode-ide/blob/develop/Toolset/palettes/script%20editor/behaviors/revseeditorbehavior.livecodescript#L1024

There is also the script editor's menu bar code in a script only stack:
https://github.com/livecode/livecode-ide/blob/develop/Toolset/palettes/script%20editor/behaviors/revsemenubarbehavior.livecodescript

On Wed, Jan 2, 2019 at 11:34 AM Andre Garzia via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Bob,
>
> Yes but it is not as ergonomic. Let me tell an example from a different
> platform. I was working in WebStorm IDE in a JavaScript project. I was
> refactoring a ton of it.
>
> One of the functions worked better with a different parameter order than
> what I originally used. I could select the function declaration, use the
> refactor contextual menu, use "change signature" and alter the param order.
> The IDE then made sure that all code that called that function was changed
> to support the new order automatically.
>
> There was a piece of code inside a function that was useful elsewhere.
> Click refactor, select "extract to new function", fill the new function
> name. It creates a new function and place a call to that function in the
> original place where it was.
>
> These are just two examples. Those refactor tools go much deeper than that.
> It makes it easy and even fun to rework your code.
>
> It would be hard to have the same power in LC because LC is more dynamic
> than JS in terms of scope and what is available. JS modern IDEs maintain an
> AST in memory for your software so that when you refactor, they can locate
> and fix the side effects of your changes. It is more powerful and flexible
> than text replacements because the IDEs actually understand the code
> through having their own parser and stuff.
>
> Buut some of it could be done in LC with simple text replacement based
> tools.
>
> Is there a way to "safely" add to LC contextual menu in the script editor?
>
> On Mon, Dec 31, 2018, 17:33 Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com wrote:
>
> > Find/Replace works great. I've done it a few times, so long as the thing
> > you are finding has a unique name that cannot be a part of any other bit
> of
> > code, you should be fine. Backup your stack of course before doing
> > something so drastic.
> >
> > A while ago, the LC dev team optimized the search engine so that it is
> > orders of magnitude faster.
> >
> > Bob S
> >
> >
> > > On Dec 30, 2018, at 11:57 , Andre Alves Garzia via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> > >
> > > Malte,
> > >
> > > So happy that you're back here my friend. I too spent some time away.
> > >
> > > So, refactoring and constantly trying to erase mistakes of my past
> > coding self are a constant here. I wish we had better refactoring tools
> so
> > that we could rename a handler and all code that called that handler was
> > fixed, or stuff such as rename variable...
> > >
> > > Cheers
> > >
> > > andre
> >
> >
> > ___
> > 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: Refactoring is your friend / moving from 6.x to 9.x

[Andre Garzia via use-livecode]

Bob,

Yes but it is not as ergonomic. Let me tell an example from a different
platform. I was working in WebStorm IDE in a JavaScript project. I was
refactoring a ton of it.

One of the functions worked better with a different parameter order than
what I originally used. I could select the function declaration, use the
refactor contextual menu, use "change signature" and alter the param order.
The IDE then made sure that all code that called that function was changed
to support the new order automatically.

There was a piece of code inside a function that was useful elsewhere.
Click refactor, select "extract to new function", fill the new function
name. It creates a new function and place a call to that function in the
original place where it was.

These are just two examples. Those refactor tools go much deeper than that.
It makes it easy and even fun to rework your code.

It would be hard to have the same power in LC because LC is more dynamic
than JS in terms of scope and what is available. JS modern IDEs maintain an
AST in memory for your software so that when you refactor, they can locate
and fix the side effects of your changes. It is more powerful and flexible
than text replacements because the IDEs actually understand the code
through having their own parser and stuff.

Buut some of it could be done in LC with simple text replacement based
tools.

Is there a way to "safely" add to LC contextual menu in the script editor?

On Mon, Dec 31, 2018, 17:33 Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com wrote:

> Find/Replace works great. I've done it a few times, so long as the thing
> you are finding has a unique name that cannot be a part of any other bit of
> code, you should be fine. Backup your stack of course before doing
> something so drastic.
>
> A while ago, the LC dev team optimized the search engine so that it is
> orders of magnitude faster.
>
> Bob S
>
>
> > On Dec 30, 2018, at 11:57 , Andre Alves Garzia via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Malte,
> >
> > So happy that you're back here my friend. I too spent some time away.
> >
> > So, refactoring and constantly trying to erase mistakes of my past
> coding self are a constant here. I wish we had better refactoring tools so
> that we could rename a handler and all code that called that handler was
> fixed, or stuff such as rename variable...
> >
> > Cheers
> >
> > andre
>
>
> ___
> 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: Refactoring is your friend / moving from 6.x to 9.x

[Andre Garzia via use-livecode]

That loop is briliant. I am tempted to place it into a command called
"unlockScreenForReal"

On Mon, Dec 31, 2018, 16:38 dunbarxx via use-livecode <
use-livecode@lists.runrev.com wrote:

> Not sure if this is still relevant in LC, but in HC, lock screen commands
> were queued. So the fix, so that one did not have to count the number of
> locks through perhaps several handlers, was:
>
> repeat until the lockScreen is false
>   unlock screen
> end repeat
>
> Craig
>
>
>
> --
> 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
>
___
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: MouseDown on Enter

[Alex Tweedly via use-livecode]

On 01/01/2019 20:39, Alex Tweedly via use-livecode wrote:

However - I'm not sure that's a very intuitive UI ("release to play"), 
so I'd probably go the extra mile and do the harder one that 
replicates the original UI. And that *is* harder, so I will try it out 
before I say any more about it ...



OK, here's a simple script that does what (I think) you want.

NB - I decided to let Malte do the hard work and used AnimationEngine to 
check whether the mouse was within each hexagon; since Malte very 
generously put AE into the public domain, I see no reason to struggle 
through the maths again :-)


The following script goes into the card script; you MUST also put a copy 
of the mouseStillDown handler into each hexagon's script. (Note there is 
no actual dependence on them being hexagons).



-- card script for hexagons
on mouseDown
   setCurrentHex
end mouseDown

on mouseUp
   setCurrentHex
end mouseUp

on mouseRelease
  setCurrentHex
end mouseRelease

on mouseStillDown pButtonNumber
  setcurrentHex
end mouseStillDown

command setcurrentHex
   local temp, tCtl, txy, x, y
   put the mouseLoc into txy
   set the itemdel to comma
   put item 1 of tXY into x
   put item 2 of txy into y
   repeat with i = 1 to 2
  put the points of grc ("P") into temp
  if  pointInPoly(x,y,temp) then
 put i && the millisecs  after msg
 exit repeat
  end if
   end repeat
end setcurrentHex


btw - you can eliminate the mouseDown, mouseUp and mouseRelease 
handlers, if you can accept the very short delay until mouseStillDown 
kicks in.


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: Refactoring is your friend / moving from 6.x to 9.x

[Paul Hibbert via use-livecode]

Malte,

I think the info you were probably looking for is buried within the dictionary 
entry for the “lockScreen” Property, maybe this should be referenced a little 
better in the dictionary entries for “lock screen” and “unlock screen”, see 
below:

LiveCode keeps count of how many times the screen has been locked. You must 
balance each unlock with a lock; if you lock the screen twice and then unlock 
it once, the screen remains locked. For example, the following pair of handlers 
draws everything while the display is still locked:

on mouseUp
lock screen-- first lock
drawStuff  -- gets locked again and unlocked in drawStuff
show image "Sprite"
unlock screen  -- now unlocked - 2 locks balanced by 2 unlocks
end mouseUp

on drawStuff
lock screen-- screen now locked twice
show field "Notify"
unlock screen  -- not unlocked yet - locked twice, unlocked once
end drawStuff

Paul

> On Dec 30, 2018, at 13:55, Malte Pfaff-Brill via use-livecode 
>  wrote:
> 
> Hey Mark,
> 
> At least it is behaviour that changed between engine releases. :-)
> Thinking of a counter here is a good way to describe the behaviour, however, 
> it is not what is written in the dictionary.
> 
> 
> "unlock screen
> 
> Sets the lockScreen property to false, updating the screen and displaying any 
> changes made since the screen was locked.“
> 
> If unlock screen sets a property, the expectation would be to take effect as 
> soon as one unlock screen is issued, as a property can only have one state. 
> Nesting is not described in the dictionary. Not that I can not live with the 
> change, that is not my point 
> ___
> 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