My personal fantasy for 2025

[richmond62]

SShot 2025-01-02 at 12.02.26.jpg (150.56 KiB) Viewed 633 times

-
A rectangular graphic with individually settable corner angles.
-

wonky2.png (8.01 KiB) Viewed 632 times

-

wonky3.png (8.2 KiB) Viewed 632 times

[tperry2x]

Would be lovely, but would need changes in-engine.
Also because it's a new object as far as the engine is concerned, it would mean that anything else reading LC stacks won't recognise it - it won't appear when read back in by anyone not using the updated engine.

[richmond62]

reading LC stacks won't recognise it

That's funny, I thought we were interested in reading OXT stacks.

it won't appear when read back in by anyone not using the updated engine.[

Surely anyone using OXT at that point would be using "the" updated engine.

Are you concerned with maintaining interoperability with LiveCode?

I am not sure why you would be as they have demonstrated on obvious interest in maintaining interoperability with OXT.

[richmond62]

rHexagon.png (1.33 KiB) Viewed 622 times

-
The ability to have rounded corners on regular polygons would also rock.

[tperry2x]

reading LC stacks won't recognise it

That's funny, I thought we were interested in reading OXT stacks.

I am, but what about people using old community versions of LC?

it won't appear when read back in by anyone not using the updated engine.[

Surely anyone using OXT at that point would be using "the" updated engine.

You'd assume so, but then I'm sure there are people who are probably going to keep using the LCC 9.6.3 engine, that don't like "Create" and don't like "OXT" for whatever reason. (if they are mac users, then probably scared off by the codesigning issue )

Are you concerned with maintaining interoperability with LiveCode?
I am not sure why you would be, as they have demonstrated on obvious [dis]interest in maintaining interoperability with OXT.

Only for people 'coming-over' from 'across-the-way', but not that I'm skilled enough to change the engine in this way anyway. I wouldn't expect LC to care one way or the other about what we do with OXT, since we are using a legacy engine as far as they are concerned. This is, I'm sure, why they want it made clear to any potential OXT users that it's nothing to do with LC now. They want to distance themselves as far away from the Community Builds of Livecode and as far away from OXT as they can. The same as I'd like to distance myself away from any association with Livecode, but I do want OXT to still be able to support Livecode Community users who want to "come on over".

[OpenXTalkPaul]

This already exists (rounded rectangle on 1 to 4 corners, not Polygons though) in the form of a Widget that Trevor Devore released about 8 years ago or more. Used for custom 'images box', but it could easily be modified to also expose the SVG Path string in PI, and add stroke width/color properties. It's in Trevore's LC-widgets repo on Github, and it works fine with version 8 of the Engine IIRC.

For polygons or arbitrarily shaped paths I think the only way to 'round' a path like that is via a miter-joins prop, which doesn't provide fine control (rounded or angular connecting points).