Re: Mapping Field Text Ranges (was Re: Interprocess Communication (IPC) under OSX)

2017-12-28 Thread Paul Dupuis via use-livecode
Mark, Thank you so much On 12/28/2017 12:45 PM, Mark Waddingham via use-livecode wrote: > On 2017-12-19 19:43, Mark Waddingham via use-livecode wrote: >> I'm pretty sure it would be possible to write a handler which takes >> the styledText array of a field in 6.7.11 and a list of old

Re: Mapping Field Text Ranges (was Re: Interprocess Communication (IPC) under OSX)

2017-12-28 Thread J. Landman Gay via use-livecode
On 12/28/17 2:42 PM, Mark Wieder via use-livecode wrote: On 12/28/2017 09:45 AM, Mark Waddingham via use-livecode wrote: 3) The char chunks are old-style (pre-5.5) byte indicies not codeunit indicies The crux of the problem Paul is having comes down to (3) which has some background to

Re: Mapping Field Text Ranges (was Re: Interprocess Communication (IPC) under OSX)

2017-12-28 Thread Mark Wieder via use-livecode
On 12/28/2017 09:45 AM, Mark Waddingham via use-livecode wrote: 3) The char chunks are old-style (pre-5.5) byte indicies not codeunit indicies The crux of the problem Paul is having comes down to (3) which has some background to explain. OMG! This is what Mr. Waddingham comes up with while

Mapping Field Text Ranges (was Re: Interprocess Communication (IPC) under OSX)

2017-12-28 Thread Mark Waddingham via use-livecode
On 2017-12-19 19:43, Mark Waddingham via use-livecode wrote: I'm pretty sure it would be possible to write a handler which takes the styledText array of a field in 6.7.11 and a list of old indicies, returning a list of new char indicies... Would that help? Paul expressed an interest in how

Re: Interprocess Communication (IPC) under OSX

2017-12-19 Thread Mark Waddingham via use-livecode
On 2017-12-19 19:43, Mark Waddingham via use-livecode wrote: On 2017-12-18 20:01, Paul Dupuis via use-livecode wrote: In principle, the same code should work equally great under OSX, but it does not. And yes, if (and when) I have time, i will track down the bugs and report them, but at the

Re: Interprocess Communication (IPC) under OSX

2017-12-19 Thread Mark Waddingham via use-livecode
On 2017-12-18 20:01, Paul Dupuis via use-livecode wrote: In principle, the same code should work equally great under OSX, but it does not. And yes, if (and when) I have time, i will track down the bugs and report them, but at the moment I was hoping for a quick fix where someone else already

Re: Interprocess Communication (IPC) under OSX

2017-12-18 Thread Richard Gaskin via use-livecode
Paul Dupuis wrote: > On 12/18/2017 1:49 PM, Richard Gaskin via use-livecode wrote: >> Which IPC method are you using? >> > Using LiveCode's open process (and related statements) vs open socket > (IP) or using files. > > I have a set of stacks that work perfectly under Windows. The main app >

Re: Interprocess Communication (IPC) under OSX

2017-12-18 Thread Paul Dupuis via use-livecode
On 12/18/2017 1:49 PM, Richard Gaskin via use-livecode wrote: > Paul Dupuis wrote: > > > I am using IPC vs Sockets... > > "IPC" is usually a generic term, encompassing a wide range of > inter-process communications methods which includes sockets, files, > shared memory, pipes, and more. > > Which

Re: Interprocess Communication (IPC) under OSX

2017-12-18 Thread Richard Gaskin via use-livecode
Paul Dupuis wrote: > I am using IPC vs Sockets... "IPC" is usually a generic term, encompassing a wide range of inter-process communications methods which includes sockets, files, shared memory, pipes, and more. Which IPC method are you using? -- Richard Gaskin Fourth World Systems

Interprocess Communication (IPC) under OSX

2017-12-18 Thread Paul Dupuis via use-livecode
I have a situation where an LC standalone (built on recent LC releases) need to communicate with a "helper app" standalone, built under LC4.6.4. The why is not really import, but it is to migrate some data that is highly dependent on how 464 handles text field character positions to versions of