LiveCode Forums.

dunbarx wrote: Mon Oct 16, 2023 4:42 pm Bad grammar? Where?

"Have", ah, autocorrect at work again. Fixed.

Perhaps did not understand the question; that is different.

I was making a point, as fan boys do now and then, that LC has within it most of the tools anyone could ever likely need, including odd use-case ones. In other words, someone simply refers one to an entry in the dictionary where the perfect solution sits ready and waiting. This happens often, and I was wondering if any other programming environment is as forthcoming.

Yes, when the question is for a basic essential as is the case here. But of course less so if we go hunting for things rarely needed.

Richard.

But of course less so if we go hunting for things rarely needed.

How does LC fair in even that sort of scenario? There may not be a definitive answer to that question.

I just recall numerous occasions where even experienced LC'ers remark about the fact that there was a function, property or command that did just what they were wishing for, but that they did not know existed.

I assume all languages with large vocabularies (suffer?) from that. Just wondering how LC fit there.

Craig

dunbarx wrote: Mon Oct 16, 2023 8:08 pm I just recall numerous occasions where even experienced LC'ers remark about the fact that there was a function, property or command that did just what they were wishing for, but that they did not know existed.

I assume all languages with large vocabularies (suffer?) from that. Just wondering how LC fit there.

I think most systems worth using will have opportunities for discovery.

I've been enjoying this fella for getting up to speed on modern CSS - this vid starts off with some tame stuff, but by halfway he's showing techniques that would require a lot of code without newer CSS, fun stuff:
https://youtu.be/y8-F5-2EIcg?si=42i_ljaBT5KjnAOM

dunbarx wrote: Mon Oct 16, 2023 4:42 pm I was making a point, as fan boys do now and then, that LC has within it most of the tools anyone could ever likely need, including odd use-case ones. In other words, someone simply refers one to an entry in the dictionary where the perfect solution sits ready and waiting. This happens often, and I was wondering if any other programming environment is as forthcoming.

It also happens to users who aren't beginners. Yesterday I knew there was a term I needed but I couldn't remember the name. I searched the dictionary for what I thought would be related terms but it didn't show up. I was at it for probably 20 minutes and never did find it until suddenly I remembered.

It's that thing where you need to know the name to look it up. I'm sure it applies to all languages.

That, my dear Jacque, may be tempus fugit (experiencing it myself) rather than the dictionary as such.

But, as the user base of LC is ageing, a cookery book as well as a dictionary might be a good thing.

And, a 'tiling an image' is a relatively generic term, it might behoove LC to get in the groove, as stuff about a backGroundPattern (is that called 'camelToe' writing?) is not the first, nor the second or third thing that is going to spring to mind.

While you and I might consider ourselves ageing trendies, those people under 50 probably look on us as a spent force, and the best way to disprove it is to keep pace with current jargon.

richmond62 wrote: Tue Oct 17, 2023 6:49 pm That, my dear Jacque, may be tempus fugit (experiencing it myself) rather than the dictionary as such.

Well, I wish tempus would just fugit itself and leave me alone.

That field appears to be overriding the inheritance, no? Try clearing its backgroundColor property and see if that allows the inheritance.

No!

What a bloody nuisance!
- -
This is an ongoing concern of mine.

Is there a way to guarantee that a newly created field will inherit either the backGroundColor of its stack, or of the backGroundColor of its card?

Presumably this is because while LiveCode is object-based it is not object-oriented, so strict inheritance is not present, and there does not seem to be a way to enforce it.

This does not help very much:
- -
And this seems plain warped:
- -
And does NOT help if one wants to set up a stack so that new fields will AUTOMATICALLY inherit a backGroundColor.

What happens if you turn off the opaque of the field, as SparkOut suggested a while back?

Well, unsurprisingly if one turns off the opaque of a field it becomes transparent, which is all very jolly unless you want that field to obcure something else.