XYLayoutEditPolicy [message #209640] |
Fri, 17 February 2006 14:58 |
Eclipse User |
|
|
|
Originally posted by: harsh.ti.com
Hi Randy,
I thought I would ask you this question since you are the author of
XYLayoutEditPolicy class.
In the createChangeConstraintCommand(ChangeBoundsRequest request, EditPart
child, Object constraint), why is it that the constraint object (in my
case a rectangle) has the correct x and y values, however, the height and
width are both -1? Is this a bug or intentional.
Thank you for your help,
Harsh
|
|
|
Re: XYLayoutEditPolicy [message #209680 is a reply to message #209640] |
Fri, 17 February 2006 19:18 |
Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
The width and height are the current values during a drag. -1 indicates the
figure should determine its desired size in that direction.
"Harsh Sabikhi" <harsh@ti.com> wrote in message
news:524696055506589548803c4cd8c9c87a$1@www.eclipse.org...
> Hi Randy,
>
> I thought I would ask you this question since you are the author of
> XYLayoutEditPolicy class.
>
> In the createChangeConstraintCommand(ChangeBoundsRequest request, EditPart
> child, Object constraint), why is it that the constraint object (in my
> case a rectangle) has the correct x and y values, however, the height and
> width are both -1? Is this a bug or intentional.
>
> Thank you for your help,
> Harsh
>
|
|
|
Re: XYLayoutEditPolicy [message #209688 is a reply to message #209680] |
Fri, 17 February 2006 21:35 |
Eclipse User |
|
|
|
Originally posted by: harsh.ti.com
Got it.
Thank you Randy. This is a separate question but do you know of any
compatiability issues wit using snapToGrip operations with 3.2? Because,
I am able to enable it but it doesn't work. I started another thread
called snapToGrip for this issue.
Thank you,
Harsh
|
|
|
Powered by
FUDForum. Page generated in 0.04398 seconds