I have converted from language to language and what I did initially was to
comment what every section of code did and how it did it (algorithms and
logic). The idea was that I should be able to delete the initial code and
reproduce it using the comments.
Then take the comments and write the cod
Okay, thank you!
JB
> On Sep 28, 2019, at 11:25 AM, Dar Scott Consulting via use-livecode
> wrote:
>
> I'm glad that was helpful. For me, when using open process as a background
> shell is knowing when things are done. In my example, I can wait for
> non-empty read results and then wait for
I would like to take the python code and convert it to LiveCode. I know
there is a cheat sheet but it is limited.
1. Has anybody attempted this and what worked and didn't work?
2. Can someone point out the problems moving from one programming language
to LiveCode?
Everyone on the list has been g
I'm glad that was helpful. For me, when using open process as a background
shell is knowing when things are done. In my example, I can wait for non-empty
read results and then wait for a few empty read results. There is probably a
better way.
> On Sep 28, 2019, at 11:57 AM, JB via use-livecode
It works for me too, Thanks
Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll
lo0 16384 82239 082239 0 0
lo0 16384 localhost ::1 82239 -82239 - -
lo0 16384 127 localhost
This works for me, LC 9.5 Mac.
on mouseup
set the cursor to watch
put "netstat -i" into p
put p -- flash
open process p for read
wait 1 seconds with messages
read from process p until empty
close process p
put it
end mouseup
> On Sep 28, 2019, at 8:05 AM, JB via use-livec
Is the handler in a script-only stack? Maybe the editor doesn't or can't
scan those.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On September 27, 2019 10:31:22 PM Sannyasin Brahmanathaswami via
use-livecode wrote:
Thanks for answers
Thank you very much!
That is what I suspected but I wanted to
have someone clarify it for me.
thanks again,
JB
> On Sep 28, 2019, at 7:46 AM, Paul Dupuis via use-livecode
> wrote:
>
> passing information (arguments, commands, etc.) to another program using
> "open process" requires that the
passing information (arguments, commands, etc.) to another program using
"open process" requires that the other program has a mechanism to listen
to interprocess messages. Most programs designed to accept a set of
command-line parameters do not have listeners for inter process
communication (IP
I provided the wrong path in the code by setting
the default folder to desktop but the code has the
correct path and do not set defaultFolder using
desktop.
The question is still the same about supplying the
arguments to the executable.
JB
> On Sep 28, 2019, at 7:05 AM, JB via use-livecode
> w
In a shell command I can execute a external program
using the following code:
on mouseUp
set the defaultFolder to desktop
put “myPic.jpg" into tFILE1
put “myPic copy.jpg" into tFILE2
put shell( "./copy" && quote & tFILE1 & quote && quote & tFILE2 & quote)
into pData
answer question
On 9/27/2019 11:29 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
No one answers the other question, so I will ask it here, as it goes to Message
Hierarchy
"put gotSomeFruit() into tBanana"
where " gotSomeFruit ()" is among the functions/handlers is found among
"stackInUse". ie.
12 matches
Mail list logo
