Some of the many reasons I dislike widgets made with LCB.

[richmond62]

underlay.jpg (11.5 KiB) Viewed 2323 times

-

Since a native iOS field is an OVERLAY on top of your card, I'm afraid it is not possible to "put" it into a group.
Maybe with some ugly tricks, but not right out of the box.

https://forums.livecode.com/viewtopic.p ... 17#p231517

[richmond62]

Having a retro moment I was looking at widgets in LC 963 (as one does) and I noticed that
a lot of them were loading when the IDE was opened: why? surely they should not load into the
system (clogging up the works) until/if I decided to use them?
-

Screenshot 2024-08-17 at 13.48.57.png (525.86 KiB) Viewed 2319 times

-
Ideally in OXT Heavy/Lite widgets should NOT load by default at IDE startup.

AND what about widgets like this:
-

Screenshot 2024-08-17 at 13.52.53.png (569.81 KiB) Viewed 2317 times

-
Who knows if they load at startup or not . . . not good.

[richmond62]

And . . .
-

Hex LEGO.png (53.92 KiB) Viewed 2310 times

-
A bit like some sort of theoretical hexagonal LEGO piece: they just will not 'play nicely' with the 'classic' controls.

[OpenXTalkPaul]

underlay.jpg
-

Since a native iOS field is an OVERLAY on top of your card, I'm afraid it is not possible to "put" it into a group.
Maybe with some ugly tricks, but not right out of the box.

https://forums.livecode.com/viewtopic.p ... 17#p231517

This is specifically about 'Native Layer' not a reason to dislike normal xBuilder widgets, which again those are rendered by libSkia that is embedded into the engine(s).
Regular non-'Native Layer' widgets can indeed be be used inside a group like any other control, and you can even reference them like 'put the name control 1' (the example assumes there's only a single widget control on the currentCard).

[OpenXTalkPaul]

Having a retro moment I was looking at widgets in LC 963 (as one does) and I noticed that
a lot of them were loading when the IDE was opened: why? surely they should not load into the
system (clogging up the works) until/if I decided to use them?

How is it any different from the half a million IDE script libraries, front scripts and back scripts (actually I think those are probably worse, because some of them are subscribed to bunches of IDE messages), and other stacks that get 'loaded' into memory, they're 'Lazy Loaded' just sitting there waiting to be called on before actually doing anything, they're not really take up any significant system resources, at least not until they are being used (and ONLY while being used).
But if they're not marked as being part of the IDE, you can unload or uninstall them from that Extension Manager stack.
You can always check 'the loadedExtensions to see what sorts of Widgets are available to use (ie have been 'Lazy Loaded').

[OpenXTalkPaul]

Ideally in OXT Heavy/Lite widgets should NOT load by default at IDE startup.

AND what about widgets like this:
-
Screenshot 2024-08-17 at 13.52.53.png
-
Who knows if they load at startup or not . . . not good.

There's a few Widgets, like the Tree View and the Color Swatch and of course SVG Icon widget, which are used by the IDE, if you remove them you'll have to rewrite some stacks to use something else. I have no intention of doing that, in fact I think Widgets offer a whole world of better possibilities, and I basically prefer them to 'classic'' now.