AW: AW: AW: Why do I still need MacToISO, when working with UTF-8?

Yep. And no, I didn't tested textEncode(myFile,"CP1252") Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von Kay C Lan via use-livecode Gesendet: Mittwoch, 18. Januar 2017 05:36 An: How to use LiveCode

Re: What has changed in MacOS 10.12 in handling code pages?

What I should have added: If you set a font for your stack, does that fix the problem, i.e. you still leave the font setting for Menus and Fields empty. If not, if you specify a font for your Menus and Fields does that fix the problem? Obviously you have to choose a font you know has Umlaut etc.

Re: What has changed in MacOS 10.12 in handling code pages?

I was thinking that this might have something to do with the installed fonts you have and maybe some sort of substitution if the font you used with your pre-10.12 install is not available with your new install. Interestingly I've just done a test and got a rather unusual result when trying to

Re: AW: AW: Why do I still need MacToISO, when working with UTF-8?

On Tue, Jan 17, 2017 at 1:24 AM, Mark Waddingham via use-livecode wrote: > > However, the 'endpoints' (i.e. where the developer can 'see' encoded text > output - e.g. when writing to a file, or encoding for a URL) had to remain > as before otherwise all existing

Re: What has changed in MacOS 10.12 in handling code pages?

On Tue, Jan 17, 2017 at 10:11 AM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > It was a different world back then. I suppose if Zimbabwe had invented > computers, we would have been upset that the whole industry revolved around > Ndebele. > sometimes, Bob you are

AW: Help: Odd menu behavior under LC6.7.11 on OSX

This "odd behavior" is indeed a LC engine bug under OSX, from version 6.7 onward including LC9. See http://quality.livecode.com/show_bug.cgi?id=19097. Mark Waddingham has identified the cause and the fix for future releases. ___ use-livecode mailing

Re: Best practice for menus...

J. Landman Gay wrote: > On 1/17/17 2:27 PM, Richard Gaskin via use-livecode wrote: >> I was curious about performance, so I ran the test copied below, with >> these results: >> >> MenuItem: 219 ms >> As text: 10 ms > > Do the results change if you lock menus before changing them? >

Re: side effect on mac with LC

On Tue, Jan 17, 2017 at 2:44 PM, Yves COPPE via use-livecode < use-livecode@lists.runrev.com> wrote: > Sorry, but your answer is not enough clear to help me… > can you explain more with a more developed sample > Not without writing one from scratch; that one is pretty much out of my own code

Re: side effect on mac with LC

Hi, I will try it tomorrow Thank you Greetings. Yves COPPE yvesco...@mac.com What you can do is the following: When the user pushes down you register the horisontal position of the pointer and store this position for later use. This can be stored in a variabel or a custom property like

Re: side effect on mac with LC

What you can do is the following: When the user pushes down you register the horisontal position of the pointer and store this position for later use. This can be stored in a variabel or a custom property like this: global gStartH on mouseDown put the mouseH into gStartH end mouseDown

Re: Best practice for menus...

On 1/17/17 2:27 PM, Richard Gaskin via use-livecode wrote: I was curious about performance, so I ran the test copied below, with these results: MenuItem: 219 ms As text: 10 ms Do the results change if you lock menus before changing them? Manipulating menus, especially on Macs, is

Re: side effect on mac with LC

Hi, Sorry, but your answer is not enough clear to help me… can you explain more with a more developed sample ? If you mean what I think you mean, you can use "on mouseMove": on mouseup if the thumbpos of me <> the savedThumPos of this stack then --it changed doSomething end if set the

Re: Code signing - not out of the wood yet: please help!

I “think” that once you get the certificate into keychain, you no longer need to worry about “keys”. The main thing is to have, for standalones, one named: “Developer ID Application: xx” for the app. I think, if you have an installer and you sign it, it will use one named “Developer ID

Re: Best practice for menus...

At 12:49 PM -0500 1/17/2017, Paul Dupuis via use-livecode wrote: For desktop applications on Windows and OSX, I am lookingf or what people consider the best practice to be for enabling, disabling, or updating menu items based on context. You have so many ways in the LiveCode language to do

Re: side effect on mac with LC

On Tue, Jan 17, 2017 at 12:42 PM, Yves COPPE via use-livecode < use-livecode@lists.runrev.com> wrote: > Is it possible with LC to have a sliding on side effect when moving > horizontally the finger on the mouse as to let appear a « red btn » > underneath another on front with label for example «

Re: Best practice for menus...

Richard, Thanks for the timing information. It was reassuring to see changing the text was faster. In dealing with bug http://quality.livecode.com/show_bug.cgi?id=19097 I have been looking to clean up menu code and was looking for best practice feedback exactly like yours. My own inclination has

side effect on mac with LC

Hi list, I’d like to make an effect typically for mobile on a mac Is it possible with LC to have a sliding on side effect when moving horizontally the finger on the mouse as to let appear a « red btn » underneath another on front with label for example « Remove » ? You can see that on the

Re: Best practice for menus...

Paul Dupuis wrote: > For desktop applications on Windows and OSX, I am lookingf or what > people consider the best practice to be for enabling, disabling, or > updating menu items based on context. > > You have so many ways in the LiveCode language to do this: > > enable menuItem 2 of menu

Re: What has changed in MacOS 10.12 in handling code pages?

It was a different world back then. I suppose if Zimbabwe had invented computers, we would have been upset that the whole industry revolved around Ndebele. Bob S On Jan 17, 2017, at 04:32 , Tiemo Hollmann TB via use-livecode

Re: Code signing - not out of the wood yet: please help!

Not quite out of the wood yet. I have actually generated the certificates, and got them into my KeyChain, but not exactly as I expected. I get this from the Apple Developer Portal: > Download, Install and Backup > Download your certificate to your Mac, then double click the .cer file to >

Best practice for menus...

For desktop applications on Windows and OSX, I am lookingf or what people consider the best practice to be for enabling, disabling, or updating menu items based on context. You have so many ways in the LiveCode language to do this: enable menuItem 2 of menu "Edit" disable menuItem 3 or menu

Re: Code signing - not out of the wood yet: please help!

Graham, For me, one problem is that I use the signing and deployment system so seldom that I forget the idiosyncrasies when I delve back not the Apple Developer site. I then may duplicate certificates or provisioning profiles, and that confuses everything. One of the most useful buttons I

Re: Code signing - not out of the wood yet: please help!

Bill, thanks to you and to the ever-helpful Matthias. I have in fact got used to dropDMG, so I will probably stick to that. I do already have a link to the Trevor/Monte signing app, so it looks as if this is all coming together. I wonder if we are in the minority in finding all this such a

Re: Code signing - not out of the wood yet: please help!

Graham, I've had similar hair pulling experiences. Mathias' instructions are great initial steps. What you need to do after you get the developer certificate and get it into your keychain, is to actually do the signing. I've tried App Wrapper 3, which a lot of folks have used, but found that it

AW: What has changed in MacOS 10.12 in handling code pages?

Obviously it is the LC roulette, which version you have created your standalone Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von Klaus major-k via use-livecode Gesendet: Dienstag, 17. Januar 2017 12:51 An: How to use LiveCode

AW: What has changed in MacOS 10.12 in handling code pages?

Isn't that crazy? We are logging year 2017 and are still struggling with code pages, as far as you are not American, as in 1987 or 1997 or 2007 and probably still in 2027 and 2037. Who was so short brained to invent ASCII? Tiemo -Ursprüngliche Nachricht- Von: use-livecode

Re: Code signing - not out of the wood yet: please help!

Graham, - in your developer account select “Mac OS X” in the dropdown menu on the left side above the word “Certificates” - then click “All” under “Certifcates” on the left side - click the “+” sign on the right side (near the loupe) - in the next page select “Developer ID” near the bottom -

Re: What has changed in MacOS 10.12 in handling code pages?

Hi Tiemo, > Am 17.01.2017 um 11:07 schrieb Tiemo Hollmann TB via use-livecode > : > > Hello, > > while testing my migration to LC 8 and successfully solved the MacToISO > issue, I now encounter that the old LC 6 standalone version of my program > shows all

Re: What has changed in MacOS 10.12 in handling code pages?

Hi Tiemo, I do not know what changed, but I see the same. Earliest version to fix this is 6.7.6 as far as I can tell. Cheers, Malte ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and

Code signing - not out of the wood yet: please help!

Having more or less sorted code signing for a Windows app - thanks to contributors to this list - I am now trying to do the same for the Mac, but I have clearly missed some massive chunk of the work flow. I’m a registered developer. I want to distribute my apps outside of the Apple App Store.

What has changed in MacOS 10.12 in handling code pages?

Hello, while testing my migration to LC 8 and successfully solved the MacToISO issue, I now encounter that the old LC 6 standalone version of my program shows all Umlaute corrupted in all LC screens, This affects all buttons and field, where Umlaute are used. The weired thing is, that this is a