Re: adjacent objects

Richmond, I was trying to recreate "Boids" (but got distracted playing with the muckingabout stack at the same time, more on that later :-). I had each object post their position to a global list of objects when they stopped moving (or when a new recalculation cycle is declared). Then each

adjacent objects

I am aware that objects/controls are on different layers on a LiveCode card, but the end-users looking at a 2-dimensional screen they are all, apparently, on a flat surface. Has anyone any idea how a script within the mouseUp of one control could detect the presence of "adjacent" controls on

Re: adjacent objects

Hi Richmond and Walt, I tried to find out your definitions of "adjacent". Walt has its own clever situation-dependent, sometimes self-adapting definition of 2D- or 3D-neighbourhoods, perhaps too complicated for your project. You, Richmond, think at first of 'nearby' rects. I suggest to do that

Re: adjacent objects

Coincidently, I am facing the same problem as I too am trying to recreate Boids in LC. However, I’m confining myself to 2D, thinking I need to learn to walk before I can fly like the Boids! How about this: create a graphic “Region” that corresponds to your desired size/region of adjacency, and

Re: adjacent objects

On Mon, Dec 7, 2015 at 3:33 AM, Richmond wrote: > > If we imagine a chessboard . . . > > ... > > Of course, the main criticism about my idea of using a field to store prop > details is that looking up info in it > will be significantly slower than using an array. > >

Re: adjacent objects

On 06/12/15 20:44, Walt Brown wrote: Richmond, I was trying to recreate "Boids" (but got distracted playing with the muckingabout stack at the same time, more on that later :-). I had each object post their position to a global list of objects when they stopped moving (or when a new