Re: Involuntary drags
- View Source--- In Pimlical@yahoogroups.com, "CESDewar" <dewar@...> wrote:
>Thanks! Is there a way to make some events non-draggable? That is one has to open edit to change the time. I found that if I double-click the event to open edit (for a change different than schedule) I also changed the schedule; the 1 pixel move.
> Example: the following flight AA 1387 BNA-DFW departs 17:05 and arrives
> 19:15. It shows up as 17:00 to 19:10 after I have been near it with the
> cursor. The duration is kept but departure has changed.
> Is there any way to safeguard against this? The only "drag" related
> preference I could find refers to the colour of the drag box.
> The problem is that drags do SNAP to the boundary of the cell, or the
> half-boundary of the cell.
> So if you drag an item to the top half of the cell, it gets that time, and
> it gets the mid-point time of the cell if you drag it to a point below the
> Yes, it is an operator error, BUT a flaky mouse can cause this. It can also
> happen inadvertently when you click an item, as if you drag it even so much
> as one pixel, the JVM reports it as a drag operation and it's not all that
> easy for PImlical to figure out that it was inadvertent.
> What I might be able to do is put a check in to see if the item has been
> dragged into the SAME cell. I might be able, for example, to force the user
> to drag the item some MINIMUM number of pixels from its original position
> (set in a preference) before treating the operation as a drag operation. I
> do know the JVM is HORRIBLY sensitive in that even a one pixel move gets
> reported as a drag.
> That's why pimlical almost everywhere uses a mouse-up operation, rather than
> a click to invoke an event, as I found out that buttons seemed sometimes not
> to generate a click event because the JVM was looking at it as a drag
> operation (which has no meaning on a button and therefore got ignored).
> So it's an issue that could well be addressed. I'll make a note of it.
> CESD, Pimlico Software, Inc.
> . . .