Rer: Decrypt problem on Windows

The problem is platform-symmetric. That is, a string encrypted in LC on Windows will not decrypt on the Mac. Linux will not decrypt a string encrypted on the Mac, and presumably vice-versa. I did toy with the idea that the encryption keys might be device dependent, maybe the public and private

Re: Rer: Decrypt problem on Windows

Hello Neville, Could you try to textEncode the encrypted data before saving it in the custom property, and then, in the other platform, textDecode it before decrypting it? i.e. to do something like: encrypt myData using myCipher with password myPass put it into tEncryptedData put

Re: New MacBook Pro Results

I don’t know, but I’m sure others on this list do. Roger > On Dec 13, 2020, at 8:45 PM, Linda Miller via use-livecode > wrote: > > “I sure do miss Scott!” > > I have been watching videos from different conferences and enjoyed his > lectures. So, what happened to Scott? > > Linda >

Re: New MacBook Pro Results

the good news is that both are just normal stacks (as is tmControls/2), so you should be able to fix them. On Sat, Dec 12, 2020 at 3:27 PM Roger Guay via use-livecode < use-livecode@lists.runrev.com> wrote: > Thought some of you might like to know, LC 6.0 works fine in MacOS Big Sur > on the new

Re: New MacBook Pro Results

Are you referring to Scott Rossi? LC did a profile on Scott for the Locked Learning Series in May. Google “Scott Rossi Livecode” to find our what he’s been up to recently. Sent from my iPhone > On Dec 14, 2020, at 2:35 PM, Roger Guay via use-livecode > wrote: > > I don’t know, but I’m

Slow performance on Big Sur

My client is running Big Sur and says that changing cards in a stack causes a very slow, stuttering display. The background image appears in chunks and text in the fields comes in as sequential pieces. The order of the display varies, sometimes the text appears first, sometimes the background

[ANN] This Week in LiveCode 248

Hi all, Read about new developments in LiveCode open source and the open source community in today's edition of the "This Week in LiveCode" newsletter! Read issue #248 here: https://bit.ly/3njG6zy This is a weekly newsletter about LiveCode, focussing on what's been going on in and

Re: Slow performance on Big Sur

I have a customer with a brand new Mac Pro with tons of memory (and two 49 inch curved screens!) running Big Sur and he sent a video showing slow performance when populating a half dozen text fields from a custom property - took about 3 seconds (in a standalone). Marty > On Dec 14, 2020, at

Re: Slow performance on Big Sur

I also populate a field and adjust its rect from custom properties, as well as adjust some controls based on stored custom property settings. I also load an image from an unplaced background. So, lots of setup on preOpenCard. On 12/14/20 1:14 PM, Marty Knapp via use-livecode wrote: I have a

Searching this mailing list

Is there a way to search through the archives of this mailing list? ... Other than search engines like Google. Linda ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your

Re: CentOS Death in 2021

Hi Mark, Are you able to say what particular bits were broken so I know what to be on the lookout for and assess if these might affect our project? Thanks Sean Cole *Pi Digital * On Mon, 14 Dec 2020 at 01:15, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 12/13/20

Re: Slow performance on Big Sur

On 12/14/2020 2:04 PM, J. Landman Gay via use-livecode wrote: My client is running Big Sur and says that changing cards in a stack causes a very slow, stuttering display. The background image appears in chunks and text in the fields comes in as sequential pieces. The order of the display

Re: CentOS Death in 2021

Hi Richmond, You're probably right. However, with security issues constantly needing keeping up to date with, it's probably worth working out if it is worth supporting Linux at all, then. If they, LC, feel it 'is' worth supporting Linux, it is surely, then, essential to keep up with these latest

Re: CentOS Death in 2021

Sean Cole wrote: > You're probably right. However, with security issues constantly > needing keeping up to date with, it's probably worth working out > if it is worth supporting Linux at all, then. If they, LC, feel > it 'is' worth supporting Linux, it is surely, then, essential > to keep up

Re: Encrypting Stack Breaks Field References

Thanks everyone for your suggestions and help. I _guess_ I see the problem as creating fields inside an encrypted stack and referencing them to set properties, etc. So the new plan is to have an unencrypted stack in which I build the tree and connectors using code from the encrypted stack. This

Re: Slow performance on Big Sur

On 12/14/20 2:46 PM, Paul Dupuis via use-livecode wrote: On 12/14/2020 2:04 PM, J. Landman Gay via use-livecode wrote: My client is running Big Sur and says that changing cards in a stack causes a very slow, stuttering display. The background image appears in chunks and text in the fields comes

Re: Searching this mailing list

This may help: http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html Paul > On 14Dec, 2020, at 3:09 PM, Linda Miller via use-livecode > wrote: > > Is there a way to search through the

Re: Slow performance on Big Sur

Hello all, Does adding a after the command make any difference? Cheers, Panos -- On Tue, 15 Dec 2020 at 00:24, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > I also populate a field and adjust its rect from custom properties, as > well as adjust some > controls

Rer: Decrypt problem on Windows solved

> Could you try to textEncode the encrypted data before saving it in the > custom property, and then, in the other platform, textDecode it before > decrypting it? Many thanks Panos, yes, that fixed the problem. It never occurred to me that reading binary data from the custom properties of a

Re: Encrypting Stack Breaks Field References

Mark Waddingham wrote: On 12/13/20 6:02 PM, Richard Gaskin via use-livecode wrote: >> >> Copying objects is disallowed in an encrypted stack, since of course >> once an object is copied it could be pasted into an unencrypted >> stack, and thus expose the source. > > Its not the copy that will be

Re: CentOS Death in 2021

On 12/14/20 3:17 PM, Sean Cole (Pi) via use-livecode wrote: Hi Mark, Are you able to say what particular bits were broken so I know what to be on the lookout for and assess if these might affect our project? Sure. Here's the PR https://github.com/livecode/livecode/pull/7127 But note that you

Re: CentOS Death in 2021

"I wonder why LC don’t state support for later Ubuntu, Fedora or Debian builds?" I suspect that LiveCode believes that the uptake of the Linux version is insufficient to justify the effort of testing LC on those platforms. Richmond. On 14.12.20 2:20, Pi Digital via use-livecode wrote: