HandMorph position gridding

After much fun, I have a plausible mechanism that introduces a way to have a temporary cursor move on a grid rather than in single pixel steps. This is useful for painting programs that want to work on scaled up bitmaps, or perhaps for drawing programs wanting to place morphs on a grid (say, electrical component icons on a virtual breadboard?). It requires 4 new HandMorph methods, 1 small change to HandMorph>position: and either the use of a couple of properties in HandMorph or a couple of additional instvars.

Does anyone have objections to this being added? Speak soon so I know if I have to try yet another tactic.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful random insult:- Doesn't just know nothing; doesn't even suspect much.

On Mon, Dec 07, 2015 at 04:01:32PM -0800, tim Rowledge wrote:
> After much fun, I have a plausible mechanism that introduces a way to have a temporary cursor move on a grid rather than in single pixel steps. This is useful for painting programs that want to work on scaled up bitmaps, or perhaps for drawing programs wanting to place morphs on a grid (say, electrical component icons on a virtual breadboard?). It requires 4 new HandMorph methods, 1 small change to HandMorph>position: and either the use of a couple of properties in HandMorph or a couple of additional instvars.
>
> Does anyone have objections to this being added? Speak soon so I know if I have to try yet another tactic.
>

Sounds reasonable, can you post it to the inbox please?

Thanks,
Dave
 

> On 07-12-2015, at 6:56 PM, David T. Lewis <[hidden email]> wrote:
>
> On Mon, Dec 07, 2015 at 04:01:32PM -0800, tim Rowledge wrote:
>> After much fun, I have a plausible mechanism that introduces a way to have a temporary cursor move on a grid rather than in single pixel steps. This is useful for painting programs that want to work on scaled up bitmaps, or perhaps for drawing programs wanting to place morphs on a grid (say, electrical component icons on a virtual breadboard?). It requires 4 new HandMorph methods, 1 small change to HandMorph>position: and either the use of a couple of properties in HandMorph or a couple of additional instvars.
>>
>> Does anyone have objections to this being added? Speak soon so I know if I have to try yet another tactic.
>>
>
> Sounds reasonable, can you post it to the inbox please?

Done. I hope.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Long computations that yield zero are probably all for naught.

On Mon, Dec 07, 2015 at 08:26:36PM -0800, tim Rowledge wrote:
Thanks. I won't pretend to be a competent reviewer, but it looks
nicely done and has its own 'gridded cursor' method category to
identify the four new methods.

Dave