| Problem with > and . keys [message #154986] |
Thu, 21 October 2004 21:51  |
Eclipse User |
|
|
|
Originally posted by: contact.jasperassistant.com
When I try to move an object in logic example with the > and . keys I
only get the resize modes (one per each side and corner of the object)
but dont get the "move" mode. This happens when the object's
height/width is under certain minimum threshold. Is this a known problem ?
Thank you,
Peter.
|
|
|
| Re: Problem with > and . keys [message #155018 is a reply to message #154986] |
Thu, 21 October 2004 23:09  |
| Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
Move works in the logic example. First press of PERIOD key should stop at
the MOVE handle and display 4-way cursor.
"JasperAssistant" <contact@jasperassistant.com> wrote in message
news:cl970d$gu5$1@eclipse.org...
> When I try to move an object in logic example with the > and . keys I
> only get the resize modes (one per each side and corner of the object)
> but dont get the "move" mode. This happens when the object's
> height/width is under certain minimum threshold. Is this a known problem ?
>
> Thank you,
>
> Peter.
|
|
|
| Re: Problem with > and . keys [message #155091 is a reply to message #155018] |
Fri, 22 October 2004 05:29 |
| Eclipse User |
|
|
|
Originally posted by: contact.jasperassistant.com
Randy, try the following.
1. Create an empty logic diagram
2. Add a flow container object
3. Set the height of the object to 10 pixels
4. Use the period key to iterate handles. There is no move handle.
Thanks,
Peter.
Randy Hudson wrote:
> Move works in the logic example. First press of PERIOD key should stop at
> the MOVE handle and display 4-way cursor.
>
> "JasperAssistant" <contact@jasperassistant.com> wrote in message
> news:cl970d$gu5$1@eclipse.org...
>
>>When I try to move an object in logic example with the > and . keys I
>>only get the resize modes (one per each side and corner of the object)
>>but dont get the "move" mode. This happens when the object's
>>height/width is under certain minimum threshold. Is this a known problem ?
>>
>>Thank you,
>>
>>Peter.
>
>
>
|
|
|
| Re: Problem with > and . keys [message #155133 is a reply to message #155091] |
Fri, 22 October 2004 13:55 |
| Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
The move handle is there and the selection tool stops at the handle, but it
is obscured by the top-right handle.
"JasperAssistant" <contact@jasperassistant.com> wrote in message
news:cla1qj$m2r$1@eclipse.org...
> Randy, try the following.
>
> 1. Create an empty logic diagram
> 2. Add a flow container object
> 3. Set the height of the object to 10 pixels
> 4. Use the period key to iterate handles. There is no move handle.
>
> Thanks,
> Peter.
>
|
|
|
| Re: Problem with > and . keys [message #155203 is a reply to message #155133] |
Fri, 22 October 2004 19:26 |
| Eclipse User |
|
|
|
Originally posted by: contact.jasperassistant.com
Maybe it's me, but I am not able to move the object using keyboard under
the described condition.
Randy Hudson wrote:
> The move handle is there and the selection tool stops at the handle, but it
> is obscured by the top-right handle.
>
> "JasperAssistant" <contact@jasperassistant.com> wrote in message
> news:cla1qj$m2r$1@eclipse.org...
>
>>Randy, try the following.
>>
>>1. Create an empty logic diagram
>>2. Add a flow container object
>>3. Set the height of the object to 10 pixels
>>4. Use the period key to iterate handles. There is no move handle.
>>
>>Thanks,
>>Peter.
>>
>
>
>
|
|
|
| Re: Problem with > and . keys [message #155218 is a reply to message #155203] |
Fri, 22 October 2004 19:30 |
| Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
Neither can I. The accessible location for the move handle is too close to
the NW resize handle figure. The Z-order of the handles means that the
resize handle is on top of the move handle.
One workaround would be to change the way getAccessibleLocation is
implemented to search for open space among the other handles. The best
solution might be to enhance the accessibility to support to actually return
not just a location, but the actualy Handle for that location. Then, the
mouseMove would be ignored, and since the handle is already known.
calculateCursor would have to be hacked too.
Open a bug with any suggestions as to how to fix.
"JasperAssistant" <contact@jasperassistant.com> wrote in message
news:clbis5$io7$1@eclipse.org...
> Maybe it's me, but I am not able to move the object using keyboard under
> the described condition.
>
> Randy Hudson wrote:
> > The move handle is there and the selection tool stops at the handle, but
it
> > is obscured by the top-right handle.
> >
|
|
|
Powered by
FUDForum. Page generated in 0.04160 seconds
] 
Search
Help
Register
Login
Home
