LiveCode Forums

[/quote]
via a shell call.
[/quote]

But, aren't shell calls different for different operating systems and architectures
which rather begs the question?

I wouldn't doubt it for a minute.

But it would be very nice indeed if one could do everything from inwith a single programming language.

FourthWorld wrote: ↑

Wed Feb 26, 2020 4:16 pm

Not everything needs to be written in C++.

What has that got to do with the price of fish?

-
This is the sort of info that it would be useful for a standalone to have access to.

This from: https://www.micromat.com/products/machineprofile

a dark alley to go down I prefer the front door. :wink: I would suppose that "someone clever at LiveCode central" might know how to roll stuff into LiveCode so one did not have to dress up as Saruman to get at hardware details. Yes: before you mention it, "someone clever at LiveCode central" was me...

I wish the termites had seen that.

We came back to Al Ain after the summer holidays and I put a suitcase on a table, which collapsed in a puff of powder.

No bots in sight: just thousands of little wiggly insects.

My original HyperCard floppies were eaten out by a load of termites in the Arabian peninsular in 1998.

I wouldn't deny Danny Goodman's book was good in a way, but it is "of its time," and maybe I have come to expect things that are a bit more concise nowadays.

I have the 2nd edition of the Danny Goodman thing: it reads like an exercise in being as long-winded as possible: occasionally
I look up something in it so I know what to avoid when I prepare handouts for kids in my school.

I don't know about hardware IDs, but it is useful to know the physical characteristics of any hardware one might be running one's software on. on mouseUp put the machine into fld "ff" end mouseUp - machine.png - The Documentation misses quite a bit: - machine2.png - I wonder if that can differentiat...

Um: all slightly inconsistent methinks.

Mind you, I'm having a few problems at the moment
trying to work out when some Python conditional loops finish.

Both buttons 4 and 5 provide the same service inwith a web-browser: On clicking button 4 or 5 an odd, grey 'thing' appears in the browser window: - Screenshot 2020-02-24 at 12.44.15.png - Once that symbol appears one can navigate up and down a browser window by, simply, pushing the mouse forwards or...

-
https://www.macintoshrepository.org/261 ... nd-scripts

Presumably the reason buttons 4 and 5 work inwith web-browsers
is that they contain code to leverage those buttons.

What is the difference between the signal that is sent when I press button X on a USB device
that does not require a driver and on a device that does?