Ray, I also was sweating it out yesterday with a very important
project/stack that was stuck in 7.0.1 which is, as you say so full of
bugs as to be useless...but would not open in 6.6.2 (pretty stable...)
What I did was
created a new button on the first card and in my naïveté:
on mouseup
s
Before Christmas Ben mentioned that there would be iOS 64 bit abilities in
LiveCode. It’s worth noting that Sheep Herder was just updated in the app
store, with 64 bit support.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit thi
On 1/9/2015 5:15 PM, Ray wrote:
Already tried it. I'm actually sticking with 6.5.2. I can create a new
stack file from scratch in 7.0.1, save it as legacy 5.5 and then re-pen
it in 6.5.2 fine. I just can't open /my stack file/ the same way,
although it continues to open correctly and function
I have an idea. (probably a stupid idea) if you select the stack, and
copy it to the clipboard, then save the clipboarddata["objects"] to a
file..
THen in 6.5.2, grab the data in that file, shove it back into the
clipboarddata["objects"] and then "paste" does that allow you to get the
stack po
Looks like that whacks some other things. I’ll look at this on the weekend and
verify all the returned values are correct. I can’t believe I saw 25 when it
was supposed to be 23 and I didn’t catch it.
Bob S
On Jan 9, 2015, at 13:21 , Alex Tweedly
mailto:a...@tweedly.net>> wrote:
Thanks Bob -
Great I’ll update my code. I am also going to update it to accept CIDR notation
as the input so you will not be required to enter a subnet mask.
Bob S
On Jan 9, 2015, at 13:21 , Alex Tweedly
mailto:a...@tweedly.net>> wrote:
Thanks Bob - that looks really useful.
You do need one tiny tweak -
FWIW my test results were the same as Scott's, unable to reproduce this
issue.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
ambassa...@fourthworld.com
Already tried it. I'm actually sticking with 6.5.2. I can create a new
stack file from scratch in 7.0.1, save it as legacy 5.5 and then re-pen
it in 6.5.2 fine. I just can't open /my stack file/ the same way,
although it continues to open correctly and function fine in 7.0.1.
On 1/9/2015 7:
On Fri, Jan 9, 2015 at 11:57 AM, J. Landman Gay
wrote:
> Thanks so much. You've probably saved the rest of us a bunch of headache
>
Now if only they'll fix it fast enough to end mine . . .
:)
--
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
use
So when you selected “Save As…” did you choose “Legacy LiveCode Stack (5.5)”
from the Format pulldown at the bottom of the dialog?
I just created a basic stack in 7.0.1, saved it in 5.5 format, and it opened
correctly in both 5.5 and 6.7, so I have to imagine 6.5.2 should be fine.
You should tr
Scott - thanks again. I just tried that and unfortunately it doesn't work.
I forgot to mention that I've also tried 'exit to top' on the first
card's preOpenStack handler. I believe this would also stop any scripts
from running. Nonetheless, even choosing Open Stack... from Livecode
6.5.2's
Ray:
Press the button labeled “Messages” in the main toolbar. It’s a toggle. Press
it again to disable.
Regards,
Scott Rossi
Creative Director
Tactile Media, UX/UI Design
On Jan 9, 2015, at 1:41 PM, Ray wrote:
> Scott, could you help me with the exact syntax to 'turn on lock messages'?
Scott, could you help me with the exact syntax to 'turn on lock
messages'? I've always used either 'lock messages' or 'set lockMessages
to true' which I believe are the same (as I've done in the script
below). In either case lockMessages is set to false at idle so I'm not
sure what you and Mi
Thanks Bob - that looks really useful.
You do need one tiny tweak - the CIDR calculations are slightly off,
because of the "."s in theBinSubnetMask.
I added the line
replace "." with empty in theBinSubnetMask
just before
put offset("0", theBinSubnetMask) into theFirstNodeChar
to get the
I believe what Mike was suggesting was to turn on lock messages, then use “Open
Stack…" in the File menu to launch the stack. This should prevent any startup
scripts from firing, and you should then be able to choose "Save As…" and
resave the stack.
I haven’t done this with 7.0.1 but have done
On Jan 9, 2015, at 9:22 AM, Colin Holgate wrote:
> I noticed that and was going to say something, but if you go full screen you
> can see enough difference.
>
>
>> On Jan 9, 2015, at 12:16 PM, Devin Asay wrote:
>>
>>> Oddly enough I can’t see a difference in the video, but I can clearly see
On Fri, Jan 9, 2015 at 11:55 AM, J. Landman Gay
wrote:
> But you're right that problems would occur with a card or stack level
> handler that assumes a mouseEnter was always triggered by a control.
>
Right. Pretty sure I have some card level mouseEnter handlers that check
the mouseControl and a
On Jan 9, 2015, at 9:16 AM, Devin Asay wrote:
>> This feels weird replying to my own email. Had some response from this via
>> direct email and thought I would make it even easier to see the difference.
>> Here is a video for your enjoyment.
>> https://www.youtube.com/watch?v=wjXHt8MqYNY
>
Mike - thanks for the idea but even a script like this fails
on mouseUp
lock messages
go stack [legacyStackPath]
end mouseUp
The result is the file I chose is not a stack file.
So currently I can't open a stack which is a nearly two years of work in
an older version of Liveco
On 1/9/2015 12:34 PM, Dr. Hawkins wrote:
I remembered an address they have; livecode has a crashing stack.
Thanks so much. You've probably saved the rest of us a bunch of headaches.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www
On 1/9/2015 12:41 PM, Devin Asay wrote:
>It looks like that change actually happened in LC 6.7. In 6.5 no mouseEnter is
sent if there is no control object under the mouse. Starting in 6.7 a mouseEnter
is sent to the card even if there is no control object under the mouse. Is this
possibly an e
I spoke too soon. It just came back with a vengeance!! Open plugin stacks are
definitely NOT the cause of my screen flash problem. Dad gum it!!
Roger
> On Jan 9, 2015, at 12:08 PM, Roger Guay wrote:
>
> Some time ago, I reported a problem with random screen flashes related to
> unlock screen
Some time ago, I reported a problem with random screen flashes related to
unlock screen with visual effect, that came about with the release of Yosemite
and all recent releases of LC. I think I may have discovered the cause.
The problem seems to be exacerbated by having plugin stacks open. My s
On Jan 9, 2015, at 11:30 AM, Devin Asay wrote:
>
> On Jan 9, 2015, at 11:03 AM, J. Landman Gay wrote:
>
>> On 1/9/2015 8:02 AM, Peter M. Brigham wrote:
>>> Are people saying that in some newer versions of LC the mouseEnter
>>> message is not sent to the control being entered but rather direct
On Fri, Jan 9, 2015 at 10:30 AM, Dr. Hawkins wrote:
> It must still contain "garbage", so I need to send it somehow, but not
> publicly post (it could have my master key in it, which would be
> catastrophic).
I remembered an address they have; livecode has a crashing stack.
--
Dr. Richard E.
On Jan 9, 2015, at 11:03 AM, J. Landman Gay wrote:
> On 1/9/2015 8:02 AM, Peter M. Brigham wrote:
>> Are people saying that in some newer versions of LC the mouseEnter
>> message is not sent to the control being entered but rather directly
>> to the stack?
>
> No, that part behaves as it always
On Thu, Jan 8, 2015 at 10:21 AM, J. Landman Gay
wrote:
> I understand. But they can't fix it unless they can reproduce it. So you
> can either trust them or live with it until/unless someone else has the
> same issue and submits an example. The team is very keen to fix these
> issues, and crashe
On Fri, Jan 9, 2015 at 6:02 AM, Peter M. Brigham wrote:
> 'm not sure I understand. Are people saying that in some newer versions of
> LC the mouseEnter message is not sent to the control being entered but
> rather directly to the stack? If this is so, what happens to the target
> function? Does
That is definitely different. I won't need to put a background grc or
image (or whatever) to catch the mouseenter anymore, but I can see it
causing weird stuff. What about empty space in groups? Just checked, they
still behave the old way. Enter a group, but not over a control, and no
mouseente
On 1/9/2015 8:02 AM, Peter M. Brigham wrote:
Are people saying that in some newer versions of LC the mouseEnter
message is not sent to the control being entered but rather directly
to the stack?
No, that part behaves as it always did. Controls receive mouseEnter
normally. Previous versions of
I noticed that and was going to say something, but if you go full screen you
can see enough difference.
> On Jan 9, 2015, at 12:16 PM, Devin Asay wrote:
>
> >Oddly enough I can’t see a difference in the video, but I can clearly see
> >that the ball motion is much smoother on my system in 6.7.
On Jan 8, 2015, at 5:05 PM, Mark Talluto wrote:
> On Jan 8, 2015, at 12:44 PM, Mark Talluto wrote:
>
>> Hello.
>>
>> Just wanted to make a public statement about the move command on 7.0.1. We
>> made a really simple game called Dropper:
>> http://livecloud.io/dropper-game-updated-source-
Just did a test with 7.0.1, and things seem to work as I’d expect. If I put
this into a button, card, and stack:
on mouseenter
answer “button” — or “card" or “stack”
end mouseenter
the answer shows up that I would expect. If I do this:
on mouseenter
answer “button” — or “card or “stack”
p
You might turn off messages before opening the stack to see if it loads.
Also, if you're double clicking to open the stack, try using the file menu
instead.
On Fri, Jan 9, 2015 at 7:19 AM, Ray wrote:
> I'm trying a "Save As" on a stack file last saved in 7.0.1 so I can open
> it in 6.5.2, the la
I'm trying a "Save As" on a stack file last saved in 7.0.1 so I can open
it in 6.5.2, the last stable version of Livecode that I know of.
The choices are:
Legacy Livecode Stack (5.5)
Legacy Livecode Stack (2.7)
Legacy Livecode Stack (2.4)
I would imagine my copy of Livecode 6.5.2 would
I'm not sure I understand. Are people saying that in some newer versions of LC
the mouseEnter message is not sent to the control being entered but rather
directly to the stack? If this is so, what happens to the target function? Does
it still return the control the mouse is entering? I'm still u
Hi Gerry,
This is now the norm in iOS8 applications it would seem. Upon updating 17
iPads last weekend and uploading my app (which is identical in every way to
the one I installed during iOS7) each one requested on application launch
the permission for Push Notifications and Use of Camera (which a
37 matches
Mail list logo
