Edit policy not used by DelayedDirectEditHelper? [message #181891] |
Thu, 19 May 2005 21:41 |
Eclipse User |
|
|
|
Originally posted by: freddie_nurke.hotmail.com
I'm using the direct edit request to change modes on my text objects.
If a direct edit request is received, I enter edit mode.
Direct edit requests are generated by
SelectEditPartTracker#performDirectEdit by way of
DelayedDirectEditHelper. Why does DelayedDirectEditHelper send its
requests directly to the Part instead of passing them to any edit
policies the part has installed?
Thanks,
Fred
|
|
|
|
Re: Edit policy not used by DelayedDirectEditHelper? [message #182533 is a reply to message #182032] |
Wed, 25 May 2005 22:36 |
Eclipse User |
|
|
|
Originally posted by: freddie_nurke.hotmail.com
Hi Pratik,
Thanks for the reply. I think I understand now how this works, and I
now simply enter edit mode and return null in getCommand. That does the
trick.
Thanks,
Fred
Pratik Shah wrote:
> All requests go to the part, and it is the EditPart that forwards the
> requests to its EditPolicies. See AbstractEditPart#getCommand(). With
> direct editing (and other things, such as REQ_OPEN) there is usually not be
> a command that can be retrieved right away, so those cases are handled via
> performRequest().
>
> "Fred Nurke" <freddie_nurke@hotmail.com> wrote in message
> news:d6j186$mf$1@news.eclipse.org...
>
>>I'm using the direct edit request to change modes on my text objects.
>>If a direct edit request is received, I enter edit mode.
>>
>>Direct edit requests are generated by
>>SelectEditPartTracker#performDirectEdit by way of
>>DelayedDirectEditHelper. Why does DelayedDirectEditHelper send its
>>requests directly to the Part instead of passing them to any edit
>>policies the part has installed?
>>
>>Thanks,
>>
>>Fred
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02893 seconds