Re: Enabling "About MyApp"
I have a app that has the About as the last item in the Help menu. It works in the Windows build but not in the Mac build (MacOS 10.14.6). It worked in previous versions. I don’t see anything wrong. The symptoms on the Mac is that the About item is in the correct place but the script is not run when selected. LiveCode 9.6.1 Indy. Not sure why the script isn’t run. Any suggestions? Bill Vlahos > On May 11, 2020, at 4:40 PM, Richard Gaskin via use-livecode > wrote: > > GEORGE WOOD wrote: > > > How can I activate the "About MyApp" under the Apple menu? > > On other OSes the "About" item is usually the last item in the Help menu. If > you put your About item there, you'll find that when LC automatically > translates its menu objects for the Mac menu bar it'll move your About item > to the application menu. > > In fact, a similar thing happens with "Preferences". On most platforms it's > the last item in the Edit menu, and when you put a "Preferences" item there > the automatic menu bar change that LC does will put it in the application > menu as well, below About. > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > > ambassa...@fourthworld.comhttp://www.FourthWorld.com > > > ___ > 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 ___ 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
Re: Big Sur bugs
Just to prevent bugs with earlier versions of macOS, please change: if item 1 of tVersion>10 or item 2 of tVersion>15 then to: if (item 1 of tVersion=10 and item 2 of tVersion>15) or (item 1 of tVersion>10) then Kee Nethery > On Nov 15, 2020, at 9:51 AM, Marty Knapp via use-livecode > wrote: > > if item 1 of tVersion>10 or item 2 of tVersion>15 then ___ 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
Re: Big Sur bugs
Here’s a work-around for the tabbed button issue (the text of the hilited tab is white on a white background, thus unreadable) on preOpenCard if the platform is "MacOS" and BigSur() is true then repeat with x=1 to the number of btns of this stack if the menuMode of btn x of this stack is "tabbed" then set the backgroundColor of btn x of this stack to black end if end repeat else repeat with x=1 to the number of btns of this stack if the menuMode of btn x of this stack is "tabbed" then set the backgroundColor of btn x of this stack to empty end if end repeat end if pass preOpenCard end preOpenCard function BigSur --LC 9.6.1 reports "Big Sur" as version as 10.16, though Apple is calling it 11 - this covers both set the itemDelimiter to "." put the systemVersion into tVersion if item 1 of tVersion>10 or item 2 of tVersion>15 then return true else return false end BigSur Just put this in your main stack and Bob’s your uncle. Speaking of Bob, he has a customer control that circumvents the issue too. I’ll let him chime in to let you know where you can find that, —Marty ___ 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
Re: Standardizing codepoints
See the normalizeText entry in the dictionary, I think that might be what you mean. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On November 15, 2020 4:17:14 AM scott--- via use-livecode wrote: I’m a little over my head in this area so I may not be describing this quite right… Some unicode glyphs seem to be describable with different (arrangements of) codepoints. Is it possible to coerce the glyph to be described in a “standard” way? -- Scott Morrow Elementary Software (Now with 20% less chalk dust!) web https://elementarysoftware.com/ email sc...@elementarysoftware.com booth1-360-734-4701 -- ___ 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 ___ 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
Re: Standardizing codepoints
I don't know what sort of situation you are describing. I can only imagine you mean describing something like û as either u + circumflex, or circumflexed u (ie, on glyph). If you go here: https://www.unicode.org/charts/ apart from going blue in the face at the absolutely mind-blowing extent of the thing, you can isolate almost every glyph you can imagine as a single glyph (rather than a combination of several0. If you are referring to surrogate pairs: forget them quickly, they are old hat and guaranteed to give you a permanent cluster headache. Best, Richmond. On 15.11.20 12:15, scott--- via use-livecode wrote: I’m a little over my head in this area so I may not be describing this quite right… Some unicode glyphs seem to be describable with different (arrangements of) codepoints. Is it possible to coerce the glyph to be described in a “standard” way? -- Scott Morrow Elementary Software (Now with 20% less chalk dust!) web https://elementarysoftware.com/ email sc...@elementarysoftware.com booth1-360-734-4701 -- ___ 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 ___ 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
Re: Big Sur bugs
On 11/15/2020 11:27 AM, Klaus major-k via use-livecode wrote: But just enter -> Big Sur in the search field on the page and hit RETURN!:-) Thank you! ___ 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
Re: Big Sur bugs
I haven’t tested much, but LiveCode seems to work normally in Big Sur on Intel, and on the M1 chip machines there is a – in front of each menu item, but otherwise it’s working. ___ 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
Re: Big Sur bugs
Hi Paul, > Am 15.11.2020 um 17:24 schrieb Paul Dupuis via use-livecode > : > > Panos, > > Thank you for the rapid-response update! > > The link you provide presents me with the error "There is no with the id > '97748'. " > Just knowing a compatible LC release is on its way in 9.6.1 is a help, but > I'd love to see the list > of bugs if there is an alternate URL to view them. yes, the links give an error. But just enter -> Big Sur in the search field on the page and hit RETURN! :-) Best Klaus -- Klaus Major https://www.major-k.de kl...@major-k.de ___ 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
Re: Big Sur bugs
Panos, Thank you for the rapid-response update! The link you provide presents me with the error "There is no with the id '97748'. " Just knowing a compatible LC release is on its way in 9.6.1 is a help, but I'd love to see the list of bugs if there is an alternate URL to view them. On 11/15/2020 10:31 AM, panagiotis merakos via use-livecode wrote: Hello Paul, Here are the bugs that have been discovered so far, either by LC users or by us (LiveCode Ltd): https://quality.livecode.com/buglist.cgi?regetlastlist=97748 The 2 serious ones have been addressed and are to be tested in our pre-release build. There are another 2 cosmetic bugs, and one that seems to affect only the new ARM Macs. These bugfixes are expected to appear in the upcoming release of LC 9.6.2 RC-1. Kind regards, Panos -- On Sun, 15 Nov 2020 at 17:05, Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: So Big Sur was released on the 12th. It is not our in user's hands. Does anyone (or LiveCode corporate) have any update about Big Sur compatibility? We have customer's inquiring. We can not afford the time to jump through Apple's hoops for any of their beta versions. Now that the release is out, we can start testing our apps with it IF we can get it installed over one of our Catalina VMs but it would be nice to know what testing LC Ltd has done or others have done? On 10/8/2020 8:31 PM, Marty Knapp via use-livecode wrote: In my testing of LC apps running under Big Sur I have run into the following bugs running LC 9.6.1: 1) Tabbed buttons: The background of the highlighted tab is now white by default. Since LC renders the text for the highlighted button as white, it is not readable until you switch to another tab. Work-around - set the backgroundColor of the button to black. Bug report 22879 2) Window Shape: Setting the windowShape of a stack to an imported image no longer works. It will show the rectangle of the stack. Bug report 22880 3) SystemVersion: Big Sur is designated by Apple as version 11 but LC will report it as 10.16. Easy enough to code around until it’s fixed. Bug report 22887 4) Printing: LC hangs as I mentioned in a previous post. Bug report 22930 ___ 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 ___ 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 ___ 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 ___ 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
Re: Sensor questions
Hi Graham, By no means a complete answer to your question, but if you have a bluetooth sensor to work with, take a look at mergBLE. I don't think I'd be confident enough to code with it for an abstract case, but if you have an actual unit to test I would expect you should be able to interface to it. Ben On 13/11/2020 13:26, Graham Samuel via use-livecode wrote: A couple of more general questions about mobile sensor functions in LC. 1. The dictionary seems to offer messages only from those sensors which are associated with native sensors in the device such as an accelerometer. Suppose I have an external sensor, for example a heart monitor connected via Bluetooth - how do I access that? 2. If a script processes sensor input by responding to messages from the sensor as they come in (as for example it does with locationChanged messages associated with GPS), what happens when the processing time for the sensor message exceeds the time between sensor inputs? Is it necessary for the script to detect that an instance of the message is already running, or does LC itself inhibit this recursion-like behaviour? Up to now I have kind of dealt with this by limiting the processing of locationChanged messages via a timer, but this is not a general solution. Can anyone explain what happens - I think the answer lies in the message queue, which I don’t fully understand. Graham ___ 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 ___ 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
Re: Big Sur bugs
Hello Paul, Here are the bugs that have been discovered so far, either by LC users or by us (LiveCode Ltd): https://quality.livecode.com/buglist.cgi?regetlastlist=97748 The 2 serious ones have been addressed and are to be tested in our pre-release build. There are another 2 cosmetic bugs, and one that seems to affect only the new ARM Macs. These bugfixes are expected to appear in the upcoming release of LC 9.6.2 RC-1. Kind regards, Panos -- On Sun, 15 Nov 2020 at 17:05, Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: > So Big Sur was released on the 12th. It is not our in user's hands. > > Does anyone (or LiveCode corporate) have any update about Big Sur > compatibility? We have customer's inquiring. We can not afford the time > to jump through Apple's hoops for any of their beta versions. Now that > the release is out, we can start testing our apps with it IF we can get > it installed over one of our Catalina VMs but it would be nice to know > what testing LC Ltd has done or others have done? > > > On 10/8/2020 8:31 PM, Marty Knapp via use-livecode wrote: > > In my testing of LC apps running under Big Sur I have run into the > following bugs running LC 9.6.1: > > > > 1) Tabbed buttons: The background of the highlighted tab is now white by > default. Since LC renders the text for the highlighted button as white, it > is not readable until you switch to another tab. Work-around - set the > backgroundColor of the button to black. Bug report 22879 > > > > 2) Window Shape: Setting the windowShape of a stack to an imported image > no longer works. It will show the rectangle of the stack. Bug report 22880 > > > > 3) SystemVersion: Big Sur is designated by Apple as version 11 but LC > will report it as 10.16. Easy enough to code around until it’s fixed. Bug > report 22887 > > > > 4) Printing: LC hangs as I mentioned in a previous post. Bug report 22930 > > ___ > > 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 > > > ___ > 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 > ___ 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
Re: Big Sur bugs
So Big Sur was released on the 12th. It is not our in user's hands. Does anyone (or LiveCode corporate) have any update about Big Sur compatibility? We have customer's inquiring. We can not afford the time to jump through Apple's hoops for any of their beta versions. Now that the release is out, we can start testing our apps with it IF we can get it installed over one of our Catalina VMs but it would be nice to know what testing LC Ltd has done or others have done? On 10/8/2020 8:31 PM, Marty Knapp via use-livecode wrote: In my testing of LC apps running under Big Sur I have run into the following bugs running LC 9.6.1: 1) Tabbed buttons: The background of the highlighted tab is now white by default. Since LC renders the text for the highlighted button as white, it is not readable until you switch to another tab. Work-around - set the backgroundColor of the button to black. Bug report 22879 2) Window Shape: Setting the windowShape of a stack to an imported image no longer works. It will show the rectangle of the stack. Bug report 22880 3) SystemVersion: Big Sur is designated by Apple as version 11 but LC will report it as 10.16. Easy enough to code around until it’s fixed. Bug report 22887 4) Printing: LC hangs as I mentioned in a previous post. Bug report 22930 ___ 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 ___ 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
Re: Standardizing codepoints
What do you mean with standard? Do you mean that some combined codepoints show up as one glyph and your question is if there is one codepoint for every such combination? Or do you mean that several seemingly identical glyphs might have different codepoints? Unicode actually has a good introduction on their site: https://www.unicode.org/versions/Unicode10.0.0/ch01.pdf that might answer some of your questions. :-Håkan On 15 Nov 2020, 11:16 +0100, scott--- via use-livecode , wrote: > I’m a little over my head in this area so I may not be describing this quite > right… > Some unicode glyphs seem to be describable with different (arrangements of) > codepoints. Is it possible to coerce the glyph to be described in a > “standard” way? > > -- > Scott Morrow > > Elementary Software > (Now with 20% less chalk dust!) > web https://elementarysoftware.com/ > email sc...@elementarysoftware.com > booth 1-360-734-4701 > -- > > > > > > > > > ___ > 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 ___ 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
Standardizing codepoints
I’m a little over my head in this area so I may not be describing this quite right… Some unicode glyphs seem to be describable with different (arrangements of) codepoints. Is it possible to coerce the glyph to be described in a “standard” way? -- Scott Morrow Elementary Software (Now with 20% less chalk dust!) web https://elementarysoftware.com/ email sc...@elementarysoftware.com booth1-360-734-4701 -- ___ 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
