Yeah I do that now. Maybe I’m just majoring in the minors, but it ought to just
work out of the box, and it irks me that it doesn’t. The Dev team ought to have
one dev dedicated to quashing these niggling bugs.
Sent from my iPhone
> On May 3, 2024, at 17:15, J. Landman Gay via use-livecode
>
I get it now. The way I work around this is to close all stacks and remove
from memory (or just relaunch LC,) turn off messages in the toolbar, and
open the splash stack. That prevents the other stacks from opening. Build
the standalone and you shouldn't have any trouble, except for remembering
Interesting. As I’ve mentioned I install and provide IT support for copiers and
printers. Ever since Windows 8 (I believe) Microsoft has been providing built
in drivers for these devices, and they use what is called a WSD (Windows
Service Daemon) port instead of a typical TCP/IP port.
If you
I think I have solved (but not resolved) the mystery. My main stack has a lot
of behaviors, which of course are enumerated in the stackFiles.
When the standalone is created, the builder closes the copy of the main stack
but it apparently leaves all the COPIES of the behavior stacks in memory.
There was a problem in the past where standalones were LC IDE, LC Instaler and
standalones were crashing on startup.
>>
This is what Panos wrote about it:
We recently fixed a bug (affecting mainly Windows 11) where the LC
installer, the LC IDE and Windows standalones were crashing on startup. It
Okay I think I traced the issue down to the fact that I “start using” a LOT of
stacks, 64 to be exact, and I think that includes all the behaviors as well as
the libraries. When I quit (or Livecode deletes) the mainStack, it does NOT
delete all the stacksInUse.
I think my solution will be to
Jacqueline:
> In that case, I'll have to try it next time.
Yes, not merely a suggestion; already works with SB here. :)
> I get the same results as Curry,
> I get two dialogs complaining there are open stacks
Not as Curry; that's due to a partial implementation.
See follow up. But you are
I'm completely locked out -- my Mac happened to open dp8, took me to the
registration saying I wasn't recognized, and now all versions of LC take me
to the registration page. I can't login at the web site either, and trying
to reset my password doesn't email me.
very sad face
gc
On Fri, May 3,
Well I gave that a try, only using your method in the splash stack. I get the
same results as Curry, I get two dialogs complaining there are open stacks on
the second platform build, then when I try to open the Main Stack without
quitting and relaunching Livecode, I get the dialog for every
In that case, I'll have to try it next time.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 3, 2024 1:13:03 PM Curry Kenworthy via use-livecode
wrote:
Code in use 4 years, no issues; restores LC's own original SB technique!
I think the problem is in the splash stack, which is where the blocking
handlers should go. When LC builds a standalone, it clones the one in the
IDE and creates the standalone from that. Then it reopens the original
which now triggers all the handlers in the original. You don't really need
to
Bob:
> Okay, well this is better. I only get the dialog twice,
> whether or not I delete the main stack or no.
> Standalone builder is leaving files open from the standalone
> that ought not be left open.
Yes, that’s what this last part does - Comments edited for clarity!
--- and only if
I can't login to my account and register the new dp8 - or login via the web
site. Something Livecode server end?
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
Okay, well this is better. When building for MacOS and Windows simultaneously,
I only get the dialog twice, whether or not I delete the main stack or no.
But if I leave Livecode running and then try to open the main stack, I get all
the dialogs.
I think the problem is that the Livecode
I had not searched the forums, but I just did for "Waiting for printer"
and "printer connections" and neither phrase turned up anything related
to the dialog that appears on startup (unfortunately). Maybe under
another search term, but the general term of "printer" returns 38
screens of forum
Bob:
> put this in the closeStack of the splash stack or the main stack?
As it says - the 'stack to build' - saving standalone from.
> Also, isn’t the problem that when opening a stack Livecode detects
> the stack being opened has the same name as one already in memory?
As Jacqueline said:
I think this has come up before, but I forget the resolution. Did you search
the forums?
Bob S
> On May 3, 2024, at 10:40 AM, Paul Dupuis via use-livecode
> wrote:
>
> When LC 9.6.11 or 9.6.12rc1 starts up OR (more importantly to me) Standalones
> build with either of those versions
When LC 9.6.11 or 9.6.12rc1 starts up OR (more importantly to me)
Standalones build with either of those versions starts up, on Windows
11, there is a dialog that appear stating "Waiting for printer
connections..."
This dialog may appear on earlier versions - I forget if I had seen it
OK so in the process of all this, my original stack Forms Generator 8 has been
OVERWRITTEN with the version the Standalone Builder created. So… anybody on
this list do NOT follow the instructions in this thread, unless you make
backups of all your stacks first, which thankfully I have done.
Also, isn’t the problem that when opening a stack Livecode detects the stack
being opened has the same name as one already in memory?
Bob S
> On May 3, 2024, at 9:39 AM, Bob Sneidar via use-livecode
> wrote:
>
> Hi Curry.
>
> I use a Splash Stack which then opens what I call the
Hi Curry.
I use a Splash Stack which then opens what I call the mainStack. Should I put
this in the closeStack of the splash stack or the main stack?
Bob S
On May 3, 2024, at 8:38 AM, Curry Kenworthy via use-livecode
wrote:
Simplest way – In card 1 of main stack to build:
on closestack
I did the pre’s as well. What about “before”?
Bob S
> On May 3, 2024, at 9:29 AM, J. Landman Gay via use-livecode
> wrote:
>
> I think the pre* handlers would need it too but try without and see how it
> goes. It depends on where they are in the message hierarchy.
>
> --
> Jacqueline
I think the pre* handlers would need it too but try without and see how it
goes. It depends on where they are in the message hierarchy.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 3, 2024 10:29:13 AM Bob Sneidar via
Unfortunately that is not working. I put the function that checks in the script
of the mainStack, and that script gets set as a backScript on preOpenstack so
that all the handlers in that stack are available in a Windows standalone (when
the Windows builder breaks out all the sub stacks, the
Bob:
> I have about had it with the Standalone asking me if I want to
> save, purge or cancel for stacks that are already open.
Simplest way – In card 1 of main stack to build:
on closestack
--- curryk 2020 no-purge LC build:
if the environment is "development" then
lock messages
Hi Marty.
I really do want to convert to Levure, but I had a lot of refactoring to do to
completely cut over to Andre’s Publish and Subscribe framework before I do
that, and I am waiting until that is completed. I am just at the point now, so
maybe that will be my next project.
Bob S
> On
Hi Jacque.
I did attempt to deploy this solution a while back, but for whatever reason it
failed to work, but I’m sure I missed something. I’m curious, should this also
be applied to (pre) openCard / closeCard handlers as well?
Thanks this is the simplest explanation I have seen.
Bob S
>
27 matches
Mail list logo
