Dave wrote:
Yes, time would work, or would be better to have it so you had to
mouse up, mouse down (select the object) and then mouse down again to
move it. In conjunction with this, would it be better to have an area
of the object that must be clicked on before movement is allowed?
Obviou
Hi,
That sounds reasonable. Then to move the object less than the slop
rect would have to be achieved using the cursor keys? Do the keys
work on all objects? I seem to remember some issues with this in the
past, but can't remember the details.
All the Best
Dave
On 26 Feb 2007, at 15:07,
On Mon, 26 Feb 2007 13:23:08 +, Dave wrote:
> Hi,
>
> Yes, time would work, or would be better to have it so you had to
> mouse up, mouse down (select the object) and then mouse down again to
> move it.
Sorry to be a dissenting voice here, but having to do *that* would
drive me crazy. :-
Hi,
Yes, time would work, or would be better to have it so you had to
mouse up, mouse down (select the object) and then mouse down again to
move it. In conjunction with this, would it be better to have an area
of the object that must be clicked on before movement is allowed?
Obviously we'
Hi Dave,
Why not use time rather than distance? If the move was done within
200 milliseconds (or whatever is suitable), debounce. That way, you
can keep the changes even when 1 pixel away but the mouse left down
long enough.
Alternatively, you could have the rule that this debouncing only
Hi,
No, not yet. I'm not sure what the best method of "de-bouncing" would
be in this case. If anyone would care to make some suggestions then
we can talk about the various merits, decide which is the best and
I'd be happy to put in a enhancement request.
All the Best
Dave
On 23 Feb 2007,
On 2/23/07 5:09 PM, "Brad Sampson" <[EMAIL PROTECTED]> wrote:
> Sorry about the extra one... Curse Windows 98. In any program I do
> that involves objects having to look nice, which means anything I
> design for someone else... so basically everything... I lock the
> position of just about everyt
Hi Dave,
I know exactly what you mean and completely agree with you. There is
one problem though. I often use the mouse to move an object only one
pixel. Mouse "de-boucing" would force me to move objects 2 or 3
pixels into one direction and then 1 or 2 pixels into the opposite
direction.
Sorry about the extra one... Curse Windows 98. In any program I do
that involves objects having to look nice, which means anything I
design for someone else... so basically everything... I lock the
position of just about everything to prevent this. You can still move
the objects with the arrow k
On 2/23/07, Devin Asay <[EMAIL PROTECTED]> wrote:
On Feb 23, 2007, at 1:57 PM, Bob Warren wrote:
> Dave wrote:
>
>> I've been suffering in silence about this for ages!
>
> Has anyone else been driven crazy by the way in which the IDE
> selects and then moves objects? What I mean is that it's w
Devin Asay wrote:
On Feb 23, 2007, at 1:57 PM, Bob Warren wrote:
Dave wrote:
I've been suffering in silence about this for ages!
Has anyone else been driven crazy by the way in which the IDE selects
and then moves objects? What I mean is that it's way too easy to move
an object just by
On Feb 23, 2007, at 1:57 PM, Bob Warren wrote:
Dave wrote:
I've been suffering in silence about this for ages!
Has anyone else been driven crazy by the way in which the IDE
selects and then moves objects? What I mean is that it's way too
easy to move an object just by selecting it. e.
Dave wrote:
I've been suffering in silence about this for ages!
Has anyone else been driven crazy by the way in which the IDE selects
and then moves objects? What I mean is that it's way too easy to move
an object just by selecting it. e.g. you select it with a mouse down
and accidently
Dave,
Have you submitted this as a bug/enhancement to Rev QC/Bugzilla? I
would add some votes to it if it were there.
Devin
On Feb 23, 2007, at 9:23 AM, Dave wrote:
Hi,
Yes, that's it. It doesn't happen in other Application because they
"de-bounce" the mouse in one (or more) of the ways
Hi,
Yes, that's it. It doesn't happen in other Application because they
"de-bounce" the mouse in one (or more) of the ways I describe below.
All the Best
Dave
On 23 Feb 2007, at 15:36, Mark Swindell wrote:
Yes, this is a minor annoyance for me too. I think what happens is
that I select
Yes, this is a minor annoyance for me too. I think what happens is
that I select an object when the mouse is still in motion over it,
and so I drag it a few pixels. I'm not sure what the solution is
from the IDE end, but it does seem to happen more frequently in Rev
than with other apps I
Hi,
I've been suffering in silence about this for ages!
Has anyone else been driven crazy by the way in which the IDE selects
and then moves objects? What I mean is that it's way too easy to move
an object just by selecting it. e.g. you select it with a mouse down
and accidently move the m
17 matches
Mail list logo
