Re: [ANN] Release 9.6.0 DP-1

On 11/26/19 3:26 PM, Brian Milby via use-livecode wrote: I have a couple and at least one is directly targeted at mobile (7154).  6404 is Vulcan reviewed but not yet merged (and is the oldest one I have outstanding).  Both are widget updates. For the IDE I only have 1987 which had a conflict

Re: DataGrid Crash to Desktop Revisited

On 12/18/19 4:30 PM, Bob Sneidar via use-livecode wrote: I'm not sure why this is, but I think it's because the datagrid library does something internernally that triggers another selectionChanged, causing an infiinite loop, forcing the engine to bail out. Yes, that's what I would expect.

Re: DataGrid Crash to Desktop Revisited

This is likely the culprit in the datagrid library. There are a number of places where it is called: private command _SelectionChanged pPreviouslyHilitedIndexes dispatch "selectionChanged" with sHilitedIndexes, pPreviouslyHilitedIndexes end _SelectionChanged I think what is needed is a way

DataGrid Crash to Desktop Revisited

Hi all. I have isolated the issue I presented some time ago, where selecting a record in a datagrid crashed Livecode to desktop. It can be reproduced easily enough. Create a stack with a single datagrid, add 2 records. In the script of the datagrid have a selectionChanged handler like so:

Re: using stdout

I found that c code. It is for a server-socket and client-socket. Two separate programs which we could call from live code with a shell command and give arguments if needed. JB > On Dec 18, 2019, at 12:56 PM, doc hawk via use-livecode > wrote: > > > On Dec 18, 2019, at 12:51 PM, JB via

Re: using stdout

On Dec 18, 2019, at 1:24 PM, JB via use-livecode wrote: > > Thank you very much! > You’re quite welcome. > I will be playing around with these a lot. > I’m interested to see what you do with it. Also, at the conference this year, I asked panagiotis, who bounced me to Mark on the

Re: using stdout

Thank you very much! I will be playing around with these a lot. JB > On Dec 18, 2019, at 1:20 PM, doc hawk via use-livecode > wrote: > > > On Dec 18, 2019, at 1:03 PM, JB via use-livecode > wrote: >> >> Actually as I said in the first post I do not really need it. I was >> reading the

Re: using stdout

On Dec 18, 2019, at 1:03 PM, JB via use-livecode wrote: > > Actually as I said in the first post I do not really need it. I was > reading the manual about something else which I have already > forgot and I ran across the code so I tried it. Investigate “sockets” in the dictionary. > > But

Re: using stdout

Actually as I said in the first post I do not really need it. I was reading the manual about something else which I have already forgot and I ran across the code so I tried it. But I am interested in messing around with writing to another application if you have any examples. Also if you needed

Re: using stdout

On Dec 18, 2019, at 12:51 PM, JB via use-livecode wrote: > > A year or so ago I was messing around with the terminal in c code > and found some code that opens two terminals and they talk to > each other. > > Is that something I can use to communicate with live code too? Conceivably, but

Re: using stdout

A year or so ago I was messing around with the terminal in c code and found some code that opens two terminals and they talk to each other. Is that something I can use to communicate with live code too? JB > On Dec 18, 2019, at 12:47 PM, doc hawk via use-livecode > wrote: > > > On Dec 18,

Re: using stdout

On Dec 18, 2019, at 12:38 PM, JB via use-livecode wrote: > > open process "/Applications/Utilities/Terminal.app" for write > write tMessage && the long time & return to stdout *That* is the problem. If you open a terminal from within livecode, that doesn’t turn it into stdout, which already

Re: using stdout

So I run the following code in live code after I have opened the terminal app. and from the message box I enter, open process "/Applications/Utilities/Terminal.app" for write write tMessage && the long time & return to stdout I get nothing. JB > On Dec 18, 2019, at 9:24 AM, Mark Wieder via

Re: using stdout

I really don’t use the shell or terminal much. When you say it is awkward I suspect I did not do it right. All I did was open the terminal and use open with the path and it opened live code. Should I have written something else? Am I supposed to launch a process? JB > On Dec 18, 2019, at

Re: using stdout

On Dec 18, 2019, at 11:06 AM, Bob Sneidar via use-livecode wrote: > > Well, sudo already offers a mechanism to prevent volatile teminal activity. But that’s a privilege restriction about superuser. Generally, I would think that a process shouldn’t be able to write to a random other

Re: using stdout

On 12/18/19 9:49 AM, JB via use-livecode wrote: Well I tried it on OS X 10.11 using Livecode 4.6.2 and the application launches then I create a new main stack and use the message box to enter your code and nothing happens. I don't have anything that old to test with, but it works with OSX

Re: using stdout

Well, sudo already offers a mechanism to prevent volatile teminal activity. Bob S > On Dec 18, 2019, at 11:02 , doc hawk via use-livecode > wrote: > >> I didn’t know you needed to launch it from >> the command line. > > Without that, I don’t think that livecode could be associated with any

Re: using stdout

On Dec 18, 2019, at 9:36 AM, JB via use-livecode wrote: > > I didn’t know you needed to launch it from > the command line. Without that, I don’t think that livecode could be associated with any particular terminal. In fact, I suspect that OSX would block any attempt from any non-descendent

Re: using stdout

Well I tried it on OS X 10.11 using Livecode 4.6.2 and the application launches then I create a new main stack and use the message box to enter your code and nothing happens. JB > On Dec 18, 2019, at 9:24 AM, Mark Wieder via use-livecode > wrote: > > On 12/18/19 7:01 AM, JB via use-livecode

Re: using stdout

I didn’t know you needed to launch it from the command line. Thanks, JB > On Dec 18, 2019, at 9:24 AM, Mark Wieder via use-livecode > wrote: > > On 12/18/19 7:01 AM, JB via use-livecode wrote: >> This isn’t something I need but I read in a older manual >> you can write to the terminal using

Re: using stdout

On 12/18/19 7:01 AM, JB via use-livecode wrote: This isn’t something I need but I read in a older manual you can write to the terminal using stdout. It said the terminal needs to be open and you use code like below to log or write to the terminal; put "Hello world." into tMessage write

Re: Make LC fully localizable!

On 12/18/2019 5:50 AM, Klaus major-k via use-livecode wrote: Hi all (non-english) LC developers, FYI: I just filed an enhancement request to make LC fully localizable, which is currently not the case! Feel free to add a comment: Perhaps

using stdout

This isn’t something I need but I read in a older manual you can write to the terminal using stdout. It said the terminal needs to be open and you use code like below to log or write to the terminal; put "Hello world." into tMessage write tMessage && the long time & return to stdout When I run

Re: Missing keys in datagrid?

Hi Trevor, > Am 18.12.2019 um 13:51 schrieb Trevor DeVore via use-livecode > : > On Wed, Dec 18, 2019 at 6:40 AM Klaus major-k via use-livecode < > use-livecode@lists.runrev.com> wrote: >>> ... >>> So my guess is that you are populating the DataGrid with data that only >> has >>> 10 columns.

Re: Missing keys in datagrid?

On Wed, Dec 18, 2019 at 6:40 AM Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Trevor, > > thanks for chiming in! > > > Am 18.12.2019 um 13:28 schrieb Trevor DeVore via use-livecode < > use-livecode@lists.runrev.com>: > > > > On Wed, Dec 18, 2019 at 2:38 AM Klaus

Re: Missing keys in datagrid?

Hi Trevor, thanks for chiming in! > Am 18.12.2019 um 13:28 schrieb Trevor DeVore via use-livecode > : > > On Wed, Dec 18, 2019 at 2:38 AM Klaus major-k via use-livecode < > use-livecode@lists.runrev.com> wrote: > ... > So my guess is that you are populating the DataGrid with data that only has

Re: Missing keys in datagrid?

On Wed, Dec 18, 2019 at 2:38 AM Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Bob, > > > Am 18.12.2019 um 01:13 schrieb Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com>: > > > > If I recall a long time ago speaking with Trevor, printkeys() does not >

[ANN] Release 9.6.0 DP-2

Dear list members, We are pleased to announce the release of LiveCode 9.6.0 DP-2. Developer Preview Release = Warning: this is not a stable release. Please ensure that you back up your stacks before testing them. Getting the Release === You can get the

Make LC fully localizable!

Hi all (non-english) LC developers, FYI: I just filed an enhancement request to make LC fully localizable, which is currently not the case! Feel free to add a comment: Best Klaus -- Klaus Major https://www.major-k.de kl...@major-k.de

Re: Table Text Livecode vs .....

Here’s another interesting observation. My table is set to Lucida Grande 13 I have some popup menus on the card set to Lucida Grande 13 Why does the text in the popup menus appear larger than the text in the Table? Thanks Terry > On 18 Dec 2019, at 08:00, Terence Heaford via use-livecode

Re: Missing keys in datagrid?

Hi Bob, > Am 18.12.2019 um 01:13 schrieb Bob Sneidar via use-livecode > : > > If I recall a long time ago speaking with Trevor, printkeys() does not > necessarily return ALL keys. AHA! OK, that explains something, but not all. Empty or not, this SHOULD list all keys, but doesn't? ... put

Re: Table Text Livecode vs .....

The setAllowsFontSmoothing function states "Font are smoothed if they are antialiased when drawn and if font smoothing is both allowed and enabled. For information on how to enable font smoothing, see the setShouldSmoothFonts(_:)