Brian:
> What about a front script for the build process that would
> intercept and discard these messages?
There you go! That might be a smooth solution. Or close the stack during
build, and offer a user preference of whether to automatically reopen.
Usually there are some fairly good
What about a front script for the build process that would intercept and
discard these messages? Could be inserted just before each action that used to
be protected by lock messages (close/open stack).
Thanks,
Brian
On Sep 19, 2018, 11:41 PM -0500, J. Landman Gay via use-livecode
, wrote:
> I
I do understand the dilemma and I can adapt. But to be fair, an
uninitialized variable doesn't require a restart of the IDE. It's possible
to script around that too, it's usually a one-liner, and doesn't have to be
inserted in as many places.
But what mainly concerned me was how it affected
Jacqueline:
> So yeah, there's repercussions. I do understand the choice the
> team had to make, but most of us were used to the old way and
> had already accommodated.
I would go further. I would say that change is not always value-free;
it's not simply a question of what people are
It my case it was "ignorance about arrays" that may my head hurt.
It would nice if the dictionary's "associations" include every keyword
related.
For example, search on array"
One find zero reference to
extents
But I found them the user guide
1) Chapter on Arrays
2) Section on Processing Text
That's what happened to the person I'm helping. He's not a sophisticated
coder and needed someone else to write a basic openstack handler a few
years ago. He's been tinkering with the stack now and then and building new
apps occasionally as it changed. He called me, very distressed, and was
Read my post, but yes if your handlers do something that can potentially
interfere with the standalone builder running (like opening a stack modally)
then things can get wiggy. You cannot simply suspend messages before building
(as I understand it) because the standalone builder needs to send
I am very late to this conversation, but does this mean that a very naive user,
devising a simple app that is going to end up as a standalone, will suddenly be
plunged into weird unguided coding issues just because the code contains
‘preOpenStack’ and similar handlers, maybe even a ‘Startup’
Oh THIS is the issue I was having where I launch a modal stack to ask for a
password when I open my mainstack! Jacques informed me I can shift-ctrl-cmd
right-click the stack and set the style to topLevel and the compiler would
proceed as normal, but Panagiotis solution looks better. I will
I was going to say something similar, but thought better of it. Sometimes you
need to step back and ask yourself, "What exactly am I trying to do here", or a
better question is, "How do I get from where I am to where I want to be (in
terms of the data) with the least amount of fuss?"
Bob S
>
> On 20 Sep 2018, at 6:18 am, Richard Gaskin via use-livecode
> wrote:
>
> Building a standalone is the whole point of the process of developing with
> LC, and now that it's so disruptive it kills the joy of choosing LiveCode.
>
> For more than a decade I've believed making the SB into a
Jacqueline:
> I'm finding that the workaround is more trouble than the
> initial issues.
Amen. This kind of workaround, I could understand if we were doing it
ourselves; although I would hope for it to be a little more elegant even
then.
But as an official workaround that comes with the
J. Landman Gay wrote:
On Tue, Sep 18, 2018 at 11:31 PM J. Landman Gay via use-livecode <
use-livecode at lists.runrev.com> wrote:
The standalone builder no longer locks messages; the docs say this:
"As an attempt to improve this situation, the code that locks messages
when closing and
On 9/19/18 1:05 PM, Geoff Canyon via use-livecode wrote:
On Tue, Sep 18, 2018 at 11:31 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
The standalone builder no longer locks messages; the docs say this:
"As an attempt to improve this situation, the code that locks
In Navigator when you double-click a control to open its script, if it has
a behavior, that script opens automatically.
On Mon, Sep 17, 2018 at 3:00 PM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I have a development menu with all the behaviors and script only stacks
On Tue, Sep 18, 2018 at 11:31 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
> The standalone builder no longer locks messages; the docs say this:
>
> "As an attempt to improve this situation, the code that locks messages
> when closing and opening stacks for
FYI
I'm caching downloaded documents in an iOS app. I was storing the
path/filename in a local db and checking in subsequent launches to see if
the document needed a download. A demo went horribly wrong when we had no
network access. I downloaded all the documents THEN did a small app fix and
off
I currently use several plug-ins:
RevNavigator by Geoff Canyon
LCStackBrowser by Peter Haworth
lctaskList by Bill Blavhos
4WDevo by Richard Gaskin. FourthWorld
revArrayBrowser by unknown
DataGridHelper by zryip theSlug
There are several of these that I automatically load on LC Startup and
others,
Hello,
I use the http://lessons.livecode.com/m/4069/l/881992-creating-a-custom-plist
to create a custom info.plist for my app. But i need to modify it for each
build to change CFBundleVersion and CFBundleShortVersionString.
How let the standalone builder modify the CFBundleVersion and
Sorry, the correct link is
http://livecodeshare.runrev.com/stack/902/
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
ControlHandles_v100 (LC Script stack)
is a group of handles (polygon and graphics) that essentialy
work, in browse mode, like the object handles in pointer mode.
The demo stack needs LC 8 or 9 because of contained widgets.
(linux users: there are also 2 browser widgets in there).
The copied
On 9/17/18 1:11 PM, Terry Judd via use-livecode wrote:
> OK - just to follow up on that, I rebuilt one of the apps using LC 9.0.1 -
> I'm still on OSX 10.10.5 so I'm using an older version of XCode - anyway, the
> app installs and launches on the iPad OK but the app icon is missing. Any
> ideas
I have been using LiveCode for a few years now. I may be "long in the Tooth"
but not when it comes to Livecode.
I have noticed that in recent postings on this list that there has been some
interest in several Plug-ins lately.
Some are "Paid for" and other are free. But what is abundantly clear is
@Brian (using the complement of your approach):
IIRC, if there is one object outside of the group
then this doesn't exist while the group is edited.
So if there is no btn "TOP" (outside of the group)
then the group is in edit mode -- any group.
___
I work on all my SOS's with a text editor instead of in the LC script
editor. If you're using Atom or Sublime Text you can generate "projects"
which are just pointers to a folder. Then on the left panel there will be
a quick-click list of SOS's to edit for that project. If you use Sublime,
you
I ran into the same problem: had to upgrade from Xcode 8.2 to 9.2,
which required that I upgrade from macOS 10.11 to 10.12. You can
download the update from Apple through the App Store @
https://support.apple.com/en-us/HT208202 but will need to log into the
Apple developer site to download
Hello Jacque,
The Standalone Builder closes and opens the stack when building a
standalone, so this means that all the messages that are sent when closing
and opening the stack will be sent. So yes, all the (pre)open*/close*
messages are expected to be sent.
The "if" block should change to:
if
The standalone builder no longer locks messages; the docs say this:
"As an attempt to improve this situation, the code that locks messages
when closing and opening stacks for standalone builds has been removed.
This means that where previously mainstacks would not receive openStack
and
I always forget about "extents". I like concise code, Alex wins. :)
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On September 18, 2018 9:25:02 PM Sannyasin Brahmanathaswami via
use-livecode wrote:
Well Alex won with "extents"
The editBackground property is global, you're either in it or not. So just
setting editBackground to false will pop you out of it, and won't do
anything if it's already false. Given the use case, that's probably enough.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software
30 matches
Mail list logo
