Re: Cross-platform font handling, and why you don't want to do it

2022-09-06 Thread Bob Sneidar via use-livecode
I'm going through my code and disabling the places where I check if a standalone is being built. I put that in there to try and get around the problem where I get alerted that stacks are in use, but that code doesn't work anyway. I still have to build one platform at a time, quitting LC between

Re: Cross-platform font handling, and why you don't want to do it

2022-09-06 Thread Neville Smythe via use-livecode
Bob Sneider wrote: > The fonts do not get included in a MacOS standalone embedding fonts in a Mac standalone worked fine for me. Have you checked that the fonts are actually in /Contents/Resources/_MacOS/ and your file path when loading is correct On the IDE problem > when I quit Livecode,

Re: Standardize Font Appearance

2022-09-06 Thread Bob Sneidar via use-livecode
Yes but I had more in mind then display properties like font size and style. Bob S On Sep 6, 2022, at 15:30 , Richard Gaskin via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: Bob Sneidar wrote: > That's great for buttons. I'd like to implement something for all > objects. My

Re: alumin(i)um

2022-09-06 Thread Bob Sneidar via use-livecode
I mean first before Alunimium. Bob S On Sep 6, 2022, at 15:22 , Mark Wieder via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: On 9/6/22 13:53, Bob Sneidar via use-livecode wrote: So the theoretical substance was dubbed Aluminum first That's "alumium" first. -- Mark Wieder

Re: Standardize Font Appearance

2022-09-06 Thread Richard Gaskin via use-livecode
Bob Sneidar wrote: > That's great for buttons. I'd like to implement something for all > objects. My goal is to be able to offer the end user a way to change > their "motif" with a single click. Imagine being able to set the > properties of an object designated as a "class object", the object >

Re: alumin(i)um

2022-09-06 Thread Mark Wieder via use-livecode
On 9/6/22 13:53, Bob Sneidar via use-livecode wrote: So the theoretical substance was dubbed Aluminum first That's "alumium" first. -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this

Re: Standalone Application Error

2022-09-06 Thread harrison--- via use-livecode
Hi Matthias, I will do that. Thanks! Rick > On Sep 6, 2022, at 6:00 PM, matthias rebbe via use-livecode > wrote: > > You need at least the xCode command line tools installed. > > If you have an Apple Developer account, then please see > here >

Re: Standalone Application Error

2022-09-06 Thread matthias rebbe via use-livecode
You need at least the xCode command line tools installed. If you have an Apple Developer account, then please see here https://developer.apple.com/download/all/?q=command%20line%20tools to see all avaiables versions of the

Standalone Application Error

2022-09-06 Thread harrison--- via use-livecode
Greetings LiveCoders, I came up against this error today: There was an error while saving the standalone application Adding ad-hoc signature failed with error: (path name to app): replacing existing signature xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools),

Re: alumin(i)um

2022-09-06 Thread Richmond Mathewson via use-livecode
Well, in Scots it's "alumeenium", which just sounds like a Scot suffered from bad spelling. On Tue, 6 Sept 2022, 23:54 Bob Sneidar via use-livecode, < use-livecode@lists.runrev.com> wrote: > Excerpt from WordOrigins.org: > > In 1808, British chemist Humphry Davy postulated the existence of a >

Re: alumin(i)um

2022-09-06 Thread Bob Sneidar via use-livecode
Excerpt from WordOrigins.org: In 1808, British chemist Humphry Davy postulated the existence of a metallic form of alumina ore, which he dubbed alumium. Davy later changed the name to aluminum. He writes in his 1812 Elements of Chemical Philosophy: "As yet Aluminum has not been obtained in a

alumin(i)um

2022-09-06 Thread Mark Wieder via use-livecode
On 9/6/22 13:19, Mike Kerner via use-livecode wrote: or the way they spell "favourites", or pronounce "Aluminum". Do you see an extra "i" in there? No? It's invisible, that's why. Yeah. About that. The "aluminium" version actually preceded "aluminum" by several years, so if anything the U.S.

Re: NAVRAD was: lcb missing manual

2022-09-06 Thread Mike Kerner via use-livecode
by the way, isn't it crazy how much overhead is required with lcb widgets? there is so...much...stuff you have to put on top just to get to the heart of the thing. and i'm never going to like the way lc embeds the comments in the source of anything. or the way they spell "favourites", or pronounce

Re: Cross-platform font handling, and why you don't want to do it

2022-09-06 Thread Bob Sneidar via use-livecode
I did some testing. It only happens when loading font files for the first time in a Livecode session from a script on MacOS. Once the font files are loaded, I can close and reopen the stack and the appearance is correct. It does NOT happen on Windows, nor does it happen with any fonts that are

Re: NAVRAD was: lcb missing manual

2022-09-06 Thread Brian Milby via use-livecode
I think the user is going to need to code the width adjustment in the resizeStack handler. Widgets can’t change their rect on their own. It has to happen from the LCS side. Brian Milby br...@milby7.com > On Sep 6, 2022, at 3:29 PM, Ralph DiMola via use-livecode > wrote: > > Mike, > >

RE: NAVRAD was: lcb missing manual

2022-09-06 Thread Ralph DiMola via use-livecode
Mike, For future reference the source is in the .lce file. The .lce is in zip format. Temporarily change the extension to .zip. You will see the lcb file in there. Also when you install it the source will be in the extension folder. But since I posted .lce I have put in comments starting with

Re: NAVRAD was: lcb missing manual

2022-09-06 Thread Mike Kerner via use-livecode
Ralph, got the source, somewhere? i'd like to learn from it. testing to begin...now. On Thu, Sep 1, 2022 at 1:32 PM Ralph DiMola via use-livecode < use-livecode@lists.runrev.com> wrote: > I took a major stab at LCB and created a new widget based on the navbar > widget. I have made 2 changes to

Re: Cross-platform font handling, and why you don't want to do it

2022-09-06 Thread Bob Sneidar via use-livecode
Sorry to drag this thread on, but it appears that using embedded fonts is worse that I first imagined. After I had set all my label fields to Acme, I repositioned them so that they were contacting the field to the right of them, and I right aligned them all so they had a consistent look. I

Re: Stylistic question.

2022-09-06 Thread Bob Sneidar via use-livecode
I went to Github, the latest version is 7.3 RC1 which is what I already had. Not sure where to look for the most recent version. Issue persists for me. Bob S > On Sep 6, 2022, at 08:11 , Bob Sneidar via use-livecode > wrote: > > I'll have a look. > > Bob S > > > On Sep 5, 2022, at 19:11

Re: Stylistic question.

2022-09-06 Thread Bob Sneidar via use-livecode
I'll have a look. Bob S On Sep 5, 2022, at 19:11 , Geoff Canyon via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: On Thu, Sep 1, 2022 at 10:32 AM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: I will however ask for just

Re: Stylistic question.

2022-09-06 Thread Geoff Canyon via use-livecode
Ha, I just realized that I responded to the Navigator part of the conversation without responding to the style part. When I wrote the "convert a control(s) to behaviors" code, I didn't think twice about what to apply it to or not -- I selected everything and converted it all. That was something

Re: Standardize Font Appearance

2022-09-06 Thread Heather Laine via use-livecode
Neville, That sounds like an incredibly useful exercise. I wonder... could you be persuaded to make that a blog post about fonts across platforms I could put on our website? If yes, contact me offlist :) Best Regards, Heather Heather Laine Customer Services Manager LiveCode Ltd

Re: Stylistic question.

2022-09-06 Thread Pi Digital via use-livecode
Arriving late to the conversation. I never put code into buttons other that enough to cover messages. These will only have enough code in them to pass on the rest of the message. Eg on mouseUp pBtn btn_nameOfButtonMUp pBtn end mouseUp on mouseRelease btn_nameOfBtnMRel end mouseRelease