15(?) years ago I wrote an app that bounced a bunch of balls across the screen. Each was a shaped-stack. It has no trouble being pretty smooth even with twenty or so stacks, as I recall. It would be more than enough for guides, especially with the 100x hardware we have today.
Positioning a stack is as simple as positioning a control, but for any translations to/from global coordinates. gc > On Aug 30, 2022, at 10:44 AM, Richard Gaskin via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I've fantasized about being able to paint directly to the window buffer > without using an object, but having done that in C back in the day I enjoy > the conveniences scripted objects bring. > > Your stack suggestion is intriguing, but how does it work in practice? > > I find the systemic overhead of dynamically reinstantiating windows to fit a > changing shape makes things a bit less smooth than I'd prefer. > > Or are you suggesting a separate stack for each guide line? That would keep > the performance up, but seems tedious to write. > > -- > Richard Gaskin > Fourth World Systems > > > > > Geoff Canyon wrote: >> He's also throwing controls into the stack to show guides for the >> alignment, and then disposing of those. So maybe in for a penny? >> If I were doing something like this I think I'd try: >> 1. A frontscript, as you say, or just setting up to receive IDE messages -- >> pretty sure there's an objectMoved IDE message or something like it. >> 2. Using stacks with the shape set as guides. >> But maybe my idea is out of date or impractical in some way. I experimented >> with some sort of auto-alignment code a long time ago. I have no memory of >> how far I got with it. >> gc >>> On Mon, Aug 29, 2022 at 1:52 PM Richard Gaskin via use-livecode < >>> use-livecode at lists.runrev.com> wrote: >>> Geoff Canyon wrote: >>> >>> > Okay, so it looks like BN Guides works by assigning behaviors to >>> > controls and temporarily adding controls to your stack as you drag >>> > things. I think this is meant to be transient as you drag controls. >>> >>> Instinctively I'd be inclined to try a frontscript before something as >>> intrusive as altering an object's behavior property for something this >>> transient. >>> >>> But Bernd does good work, so I'm curious: why this approach and not a >>> frontScript? >>> >>> -- >>> Richard Gaskin >>> Fourth World Systems > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
