Mark Waddingham wrote:
On 2021-02-03 20:07, Richard Gaskin via use-livecode wrote:
LC Server had already been ruled out (for whatever reason) in an
earlier part of the thread...
That's too bad. LC Server is LiveCode build designed specifically for
command line use.
Interesting - I don't
I don’t remember what I had for dinner on Friday. :-)
Bob S
On Feb 3, 2021, at 10:58 PM, Mark Waddingham via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
On 2021-02-03 20:07, Richard Gaskin via use-livecode wrote:
LC Server had already been ruled out (for whatever reason) in an
Hi friends,
quick question, now we have a Mac app, signed and notarized
and what not, is it also neccessary for the DMG we create from
that app for distribution?
Thanks for any insight!
Best
Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de
I just updated to Xcode 11.3 and still have the issue. With revzip included,
building with 9.6.2 it works fine *until* I codesign - either with the Levure
app packager or with AppWrapper (tried versions 3 and 4) As soon as it starts
to launch it crashes. If I take out revzip the app will open
I follow a similar approach to what Curry describes here, keeping it modular,
but I do not do any clean up at closing time. Instead I execute the necessary
routines as part of a preOpenStack handler. I then do not have to consider
which way the stack was closed. This is also what I encourage my
Performing the clean up in preOpenStack makes it happen before the stack is
visible, at least according to the dictionary.
"Unlike openStack <>, preOpenStack handlers <> are executed <> before the stack
window <> appears. Because of this, the preOpenStack handler <> is a good place
to put code
On 2/4/21 4:19 PM, Bob Sneidar via use-livecode wrote:
NVM I found this bug has already been submitted… IN 2008! LOL!
https://quality.livecode.com/show_bug.cgi?id=4617 Hey Kevin!
Looking at that, here's a (completely untested) suggestion:
The revIDEHandleCloseStackRequest handler is in the
Richard:
> they still offer a business card size with rounded corners -
> I'm taking it as a challenge to bring the card content
> down to just the essentials. ;)
> https://www.avery.com/products/cards/88220
Thanks for that link - good idea! Mini cards look great.
I doubt my own hands can
On Tue, Feb 2, 2021 at 4:25 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> JeeJeeStudio wrote:
>
> > Panos wrote:
> >> This bug report contains a workaround for smooth scrolling - hope it
> >> helps.
> >> https://quality.livecode.com/show_bug.cgi?id=19759
> >
>
Mark:
> I agree with others that this isn't a Good Idea,
> and a cleaning routine in preOpenStack would do the trick nicely.
Amen, Brother Mark! Good Idea to avoid Bad Habits.
(Agreed, except a small but crucial difference in details)
As Tore said:
> execute the necessary routines as part
On 2/4/21 6:33 PM, Curry Kenworthy via use-livecode wrote:
The preOpenStack handler is NOT ideal for this type of cleanup.
"Literally, to "clear the fields" of a stack."
(And now we also know, a "complex" stack.)
That is NOT something best done in preOpenStack.
A complex stack usually has
Thanks for testing Matthias :)
On Thu, 4 Feb 2021, 23:08 Paul Dupuis via use-livecode, <
use-livecode@lists.runrev.com> wrote:
> I should have added that we sign with entitlements (the same set LC uses)
>
> On 2/4/2021 3:56 PM, panagiotis merakos via use-livecode wrote:
> > @Marty
> >
> > If you
Is this what you're looking for?
revIDESetEdited pStackName
revIDESetUnedited pStackName
Interrogate it with: revIDEStackIsEdited pStackName
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode
Thanks Ralph. Actually what I am looking for is a message that gets sent when
the close button of a window gets clicked. The Message Watcher seems to
indicate not (or rather fails to indicate). I think this is a bug, or at least
an oversight. This means that anyone can close a stack, and
It’s my understanding that I am unable to reference objects on a card of a
stack in a preOpenStack handler. Referencing an object in the stack opens the
stack triggering a race condition which continually triggers preOpenStack. That
is from memory though.
Bob S
On Feb 4, 2021, at 2:50 PM,
Thanks for the reply Jacque. I ran the message watcher while clicking the red
dot. None of the messages that appear have anything to do with closing the
stack.
Here’s what I came up with. The closeStackRequest is NOT getting sent to the
current card as the dictionary indicates, although the
Back to the drawing board. This does NOT work when clicking the red dot.
Bob S
On Feb 4, 2021, at 3:10 PM, Bob Sneidar via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
Thanks for the reply Jacque. I ran the message watcher while clicking the red
dot. None of the messages that
I did a test before answering and the message was sent to the card of my
otherwise blank stack, after dismissing the IDE dialog. That makes me think
something is going on with your particular stack. What happens if you try
it with a plain new stack?
--
Jacqueline Landman Gay |
That looks like it would work though it isn't the variable I remember.
Probably that's what changed. Nice sleuthing.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 4, 2021 5:52:14 PM Ralph DiMola via use-livecode
wrote:
The stack is already attached to the bug report. ;)
I had some time, so I've used Marty's demo stack and created a standalone and
code signed it. I also did not add the entitlements when code signing with App
Wrapper 4.
The code signed app does not crash at startup.
-
Matthias Rebbe
Life
Bob:
> I am trying to clean up my stack (i.e. clear the fields),
> then save it when I close it
This is a good topic for LiveCode learners; I'm chiming in
I often do something similar - but with an important difference:
I perform cleanup when I save. I do NOT force an auto save.
(More on
Thanks for the response Curry and Tore.
The reason I clean up at close is because when I open the stack the next time I
do not want to remains of what I was doing before to show. It’s a small point
but it look cleaner if the first time opening the stack there is nothing in the
fields. All
There used to be a gREV* global variable that tracked the dirty status and if the stack was
dirty it put up the "do you want to save?" dialog. I can't find it now so something has
changed. When it existed, you could toggle that variable via script and the IDE wouldn't bother
you.
The IDE does
Thanks Curry. That works for the IDE, but not for the standalone. End Users do
not save their stacks, as I give them no way to do so. The stacks in my app
perform two functions: An interface to control the app and also a place to
store persistent data i.e. properties. If a user force-quits my
I should have added that we sign with entitlements (the same set LC uses)
On 2/4/2021 3:56 PM, panagiotis merakos via use-livecode wrote:
@Marty
If you have not done it already, it might be worth adding entitlements to
the codesign.
Marty,
do you experience this problem also with your demo stack and Xcode 11.3? If
so, could you create a new standalone from that demo stack and upload it
somewhere, so i could download it and try to code sign it here?
Btw. Are you code signing for web distribution or Apple store?
Regards,
Tore:
> I do not do any clean up at closing time. Instead I execute
> the necessary routines as part of a preOpenStack handler.
> I then do not have to consider which way the stack was closed.
Yes! Like you, for cleanup I also avoid that how-closed consideration.
Much easier to have a simpler
NVM I found this bug has already been submitted… IN 2008! LOL!
https://quality.livecode.com/show_bug.cgi?id=4617 Hey Kevin!
Bob S
On Feb 4, 2021, at 4:05 PM, Bob Sneidar via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
Thanks Ralph. Actually what I am looking for is a message
If the App is Signed and Notarized, it is actually best NOT to sign the
DMG. Older versions of MacOS (like Mavericks, etc.) have a problem with
signed DMGs
On 2/4/2021 11:40 AM, Klaus major-k via use-livecode wrote:
Hi friends,
quick question, now we have a Mac app, signed and notarized
and
Hi Paul,
> Am 04.02.2021 um 17:46 schrieb Paul Dupuis via use-livecode
> :
>
> If the App is Signed and Notarized, it is actually best NOT to sign the DMG.
> Older versions of MacOS (like Mavericks, etc.) have a problem with signed DMGs
thank you very much, very helpful!
> On 2/4/2021 11:40
On 2/4/21 1:52 AM, Richard Gaskin via use-livecode wrote:
With all this flexibility in one lean install, for me the pros of LC
Server for headless work are clear:
...plus the fact that there's an "include" command in the server,
allowing for things like global constants.
--
Mark Wieder
To avoid the unidentifiable developer warning in recent macOS versions, you do
need it signed. If your market is consumers, that is what they will have.
DropDMG is great.
Peter
> On Feb 4, 2021, at 8:49 AM, Klaus major-k via use-livecode
> wrote:
>
> Hi Paul,
>
>> Am 04.02.2021 um 17:46
We current ship a commercial app. We code sign, notarize, and staple our
App We then place it on a DMG using DropDMG, but do not code sign the
DMG. We distribute the DMG via our Web site and not the MacApp store.
QA testing on Catalina and Big Sur show only the usual "This (the DMG)
has been
I should add, we're not using Levure. We are using LC9.6.2rc2, we
codesign via Terminal on Mohave using Xcode 10.2.1
On 2/4/2021 3:37 PM, Paul Dupuis via use-livecode wrote:
FYI - Our App includes the revZIP library. We codesign deep via
Terminal command and get no crashes. Codesign, notarize,
Hi all.
I know we have tread this ground before, but I am trying to clean up my stack
(i.e. clear the fields), then save it when I close it BY ANY MEANS. That means
by script, by menu OR by clicking the red dot (of for WIN users the red X) in
the title bar. I need this to work in the IDE as
Hello Marty,
How is revZip used by your app? Is it used on startup?
Kind regards,
Panos
--
On Thu, 4 Feb 2021 at 22:38, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
> FYI - Our App includes the revZIP library. We codesign deep via Terminal
> command and get no crashes.
I’ve narrowed this down to the “Revolution Zip” library. If I leave that out of
Inclusions, I can build in 9.6.2 and codesign and all is well.
marty
> On Feb 3, 2021, at 2:59 PM, Mark Talluto via use-livecode
> wrote:
>
> Hi Marty,
>
> My work is with LiveCode 9.6.2 rc2 and Xcode 11.3.1.
>
Re: building a standalone in LC 9.6.2 rc2 with the “Revolution Zip” library
(crashes when codesigned)
Just filed a bug report on this - 23083
Marty
> On Feb 4, 2021, at 11:25 AM, Marty Knapp wrote:
>
> I’ve narrowed this down to the “Revolution Zip” library. If I leave that out
> of
Danke schön Klaus
Michael
___
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
David's server talk is worth a mention again! He got me into LC server. It
was so nice not to have learn php in depth as I could leverage my LC
knowledge and existing code. I use server every day.
But a question... I have always been confused with the difference between
"start using' and
Hi Marty,
i added a comment to your bug report already. I used your demo stack and cannot
replicate the crash.
I use App Wrapper 4 to code sign. I code signe for Web distribution, not for
App Store or Store installer.
I am also on Mojave (10.14.6), but i am using Xcode 11.3
Regards,
Matthias
FYI - Our App includes the revZIP library. We codesign deep via Terminal
command and get no crashes. Codesign, notarize, and staple without problems.
On 2/4/2021 2:40 PM, Marty Knapp via use-livecode wrote:
Re: building a standalone in LC 9.6.2 rc2 with the “Revolution Zip” library
(crashes
No it is not used on startup, it’s for a backup feature that the user invokes.
I am on Mojave and looks like x-code 10.1. Do you think my version of x-code
could be the issue?
All is fine when I build with LC 9.6.1. It’s when I build with 9.6.2. I’ve used
the codesigning ability of Trevor’s
@Marty
If you have not done it already, it might be worth adding entitlements to
the codesign.
https://lessons.livecode.com/m/4071/l/1293515-entitlements-for-signed-and-notarized-apps
I do not think it is the Xcode version that is the problem. I am on Mojave
as well, so I can do a quick test if
44 matches
Mail list logo
