Those are good reasons to separate the substacks from the mainstack. If you
don't plan to save changes to them, leave them attached. They open faster
that way, which is particularly noticeable on mobile.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hype
I'm not sure it's the same thing but even on a single screen the app
browser gets out of sync. If you right click on the right hand pane and
select "refresh" it fixes itself. I see this frequently when editing groups.
The same thing happens, but less frequently, on the left hand side, like
whe
Paul Dupuis wrote:
> Thank you for possible conforming, but this is not seen in the IDE.
> Jut in the built Standalone. It is also very clear that LiveCode
> thinks the mouse is 20-40 pixels towards the top of the window than
> it actually is.
> If I want to click on a button, I don't put the mou
On 6/28/2019 8:04 PM, doc hawk via use-livecode wrote:
On Jun 28, 2019, at 8:24 AM, Paul Dupuis via use-livecode
wrote:
When the standalone opens the external stack (which could be in an older stack
file format), when the mouse is in the external stack window, LiveCode thinks
the mouse is ab
On 6/28/2019 6:47 PM, Bob Sneidar via use-livecode wrote:
Also, if a stack is a part of the EXE, aren't the read only? In other words,
you cannot save things like properties by saving the stack?
Correct. But not a problem for our app as they are full desktop apps
that read and write a variety
On Jun 28, 2019, at 8:24 AM, Paul Dupuis via use-livecode
wrote:
>
> When the standalone opens the external stack (which could be in an older
> stack file format), when the mouse is in the external stack window, LiveCode
> thinks the mouse is about 30-40 pixels ABOVE where the mouse actual is
Oh that is interesting. Still, I can see one use case where separating them is
a good thing. There have been times I made a change to one or two substacks,
and only needed to replace the versions from the "Standalone" with the new
one(s). Also, if a stack is a part of the EXE, aren't the read on
On 6/28/2019 12:48 PM, Dar Scott Consulting via use-livecode wrote:
I don't know if this is related or not... I have seen the rectangle of the
window off by a similar amount when it overlaps the LiveCode IDE toolbar.
This is occurring in a a standalone, so I don't think the IDE toolbar is
a
On 6/28/2019 2:08 PM, Richard Gaskin via use-livecode wrote:
Paul Dupuis wrote:
> We have an app we're porting to LC9 (currently doing internal beta
> builds under LC9.0.5rc1) that we're seeing some weirdness when
> external stacks are opened by the standalone.
>
> This is happening under OSX. W
Paul Dupuis wrote:
> We have an app we're porting to LC9 (currently doing internal beta
> builds under LC9.0.5rc1) that we're seeing some weirdness when
> external stacks are opened by the standalone.
>
> This is happening under OSX. We've not seen it (so far) under Windows,
> but most of our ini
On 6/28/19 10:35 AM, Bob Sneidar via use-livecode wrote:
I'm under the impression that in a standalone, ALL stacks besides the one in
the executable are external stacks. That is, the Standalone Builder will copy
any substacks to a folder as individual stacks. Even in a MacOS standalone, the
pa
I've not looked inside the OSX app bundle, but on Windows, the mainstack
and its substacks are built into the EXE. What I am calling an
"external" stack is a regular livecode stack, separate from the Windows
EXE that is opened by a script in the built standalone (EXE). As in:
open stack "C:/so
I don't know if this is related or not... I have seen the rectangle of the
window off by a similar amount when it overlaps the LiveCode IDE toolbar.
> On Jun 28, 2019, at 9:54 AM, Curry Kenworthy via use-livecode
> wrote:
>
>
> Paul:
>
> > LiveCode thinks the mouse is about 30-40 pixels ABOV
Paul:
> LiveCode thinks the mouse is about 30-40 pixels ABOVE where
> the mouse actual is.
I've seen something similar with the mouse clicking at an offset. Can't
recall the context at the moment, or whether any external stacks were
involved - but I'll let you know when I remember!
Best wi
Hmmm... I'm under the impression that in a standalone, ALL stacks besides the
one in the executable are external stacks. That is, the Standalone Builder will
copy any substacks to a folder as individual stacks. Even in a MacOS
standalone, the package that is the app can be opened and you will fi
We have an app we're porting to LC9 (currently doing internal beta
builds under LC9.0.5rc1) that we're seeing some weirdness when external
stacks are opened by the standalone.
This is happening under OSX. We've not seen it (so far) under Windows,
but most of our initial QA testing is done unde
16 matches
Mail list logo
