Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » GEF » popup property dialog for each component?
popup property dialog for each component? [message #155540] Tue, 26 October 2004 05:33 Go to next message
Eclipse UserFriend
Originally posted by: grayzhu.yahoo.com

My GEF application is based on the logic example.

One thing I wanted to do is editing the property of each graphical component
by popping up a dialog after a doubleclick. I'd appreciate some pointers or
examples for this.

An alternative is using the property view, but it uses "static" blocks to
define the descriptor. I am not sure how to put an array or vector in
property view, and the number of elements can change in run time. One
analogy would be, a OR gate has more the two inputs, and the inputs could be
added during run time, how do I represent the inputs in property view?
Re: popup property dialog for each component? [message #155711 is a reply to message #155540] Tue, 26 October 2004 15:15 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: none.us.ibm.com

Look at REQ_OPEN which is sent on double-click and ENTER.

"ray zhu" <grayzhu@yahoo.com> wrote in message
news:clkn88$4je$1@eclipse.org...
> My GEF application is based on the logic example.
>
> One thing I wanted to do is editing the property of each graphical
component
> by popping up a dialog after a doubleclick. I'd appreciate some pointers
or
> examples for this.
>
> An alternative is using the property view, but it uses "static" blocks to
> define the descriptor. I am not sure how to put an array or vector in

That's just how our implementation works. Your implementation can
dynamically calculate the propertydescriptors at the time it is queried. I
considered your use case as one of the requirements when designing
IPropertySource and PropertySheetEntry.

> property view, and the number of elements can change in run time. One
> analogy would be, a OR gate has more the two inputs, and the inputs could
be
> added during run time, how do I represent the inputs in property view?
>
>
Re: popup property dialog for each component? [message #156199 is a reply to message #155711] Sat, 30 October 2004 17:45 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: grayzhu.yahoo.com

Thanks Randy for the information

REQ_OPEN is an excellent idea.

But I am still confused about the propertydescriptors approach. As you know
I wanted to list dynamic array elements as keys in property view, each
element in an array is a key, and the number of keys could change. The
reason is that the array contains object references, using the elements as
keys allows me the expand further into sub-object properties. Because
propertydescriptors are defined to be static and created with the class not
the instance, I am not sure how to dynamically calculate the
propertydescriptors, they are list of "keys" in property view as opposed to
values.

Could you be more specific about creating dynamic property? Thanks a lot!

-Ray


"Randy Hudson" <none@us.ibm.com> wrote in message
news:cllpc6$f1r$1@eclipse.org...
> Look at REQ_OPEN which is sent on double-click and ENTER.
>
> "ray zhu" <grayzhu@yahoo.com> wrote in message
> news:clkn88$4je$1@eclipse.org...
> > My GEF application is based on the logic example.
> >
> > One thing I wanted to do is editing the property of each graphical
> component
> > by popping up a dialog after a doubleclick. I'd appreciate some pointers
> or
> > examples for this.
> >
> > An alternative is using the property view, but it uses "static" blocks
to
> > define the descriptor. I am not sure how to put an array or vector in
>
> That's just how our implementation works. Your implementation can
> dynamically calculate the propertydescriptors at the time it is queried.
I
> considered your use case as one of the requirements when designing
> IPropertySource and PropertySheetEntry.
>
> > property view, and the number of elements can change in run time. One
> > analogy would be, a OR gate has more the two inputs, and the inputs
could
> be
> > added during run time, how do I represent the inputs in property view?
> >
> >
>
>
Re: popup property dialog for each component? [message #156215 is a reply to message #156199] Sun, 31 October 2004 16:29 Go to previous message
Eclipse UserFriend
Originally posted by: dyx.gmx.net

But do the descriptors have to be declared as static?

> Thanks Randy for the information
>
> REQ_OPEN is an excellent idea.
>
> But I am still confused about the propertydescriptors approach. As you=
=

> know
> I wanted to list dynamic array elements as keys in property view, each=

> element in an array is a key, and the number of keys could change. The=

> reason is that the array contains object references, using the element=
s =

> as
> keys allows me the expand further into sub-object properties. Because
> propertydescriptors are defined to be static and created with the clas=
s =

> not
> the instance, I am not sure how to dynamically calculate the
> propertydescriptors, they are list of "keys" in property view as oppos=
ed =

> to
> values.
>
> Could you be more specific about creating dynamic property? Thanks a l=
ot!
>
> -Ray
>
>
> "Randy Hudson" <none@us.ibm.com> wrote in message
> news:cllpc6$f1r$1@eclipse.org...
>> Look at REQ_OPEN which is sent on double-click and ENTER.
>>
>> "ray zhu" <grayzhu@yahoo.com> wrote in message
>> news:clkn88$4je$1@eclipse.org...
>> > My GEF application is based on the logic example.
>> >
>> > One thing I wanted to do is editing the property of each graphical
>> component
>> > by popping up a dialog after a doubleclick. I'd appreciate some =

>> pointers
>> or
>> > examples for this.
>> >
>> > An alternative is using the property view, but it uses "static" blo=
cks
> to
>> > define the descriptor. I am not sure how to put an array or vector =
in
>>
>> That's just how our implementation works. Your implementation can
>> dynamically calculate the propertydescriptors at the time it is queri=
ed.
> I
>> considered your use case as one of the requirements when designing
>> IPropertySource and PropertySheetEntry.
>>
>> > property view, and the number of elements can change in run time. O=
ne
>> > analogy would be, a OR gate has more the two inputs, and the inputs=

> could
>> be
>> > added during run time, how do I represent the inputs in property vi=
ew?
>> >
>> >
>>
>>
>
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
Previous Topic:Immersion into a component to view its sub components
Next Topic:Grid in containers for 3.0
Goto Forum:
  


Current Time: Fri Jan 24 17:46:49 GMT 2025

Powered by FUDForum. Page generated in 0.03351 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top