mhm.. the only thing I could imagine why we want backward compatibility
is for existing plugins. But I am not sure if there is actually any
plugin that would use the method... maybe though (thinking of ISA tools???)
stefan
Am 29.08.12 14:17, schrieb Michaël Michaud:
> Hi
>>> Just curious. I won
Hi
>> Just curious. I wonder why back compatibility is so important
>> for a software which is both cheap and easy to install (deployment issue ?)
> what exactly do you mean Michael?
Just wondered what is the problem for current users to migrate to an
updated version of OpenJUMP including the new
ok ;)
Am 29.08.12 05:06, schrieb edgar.sol...@web.de:
> On 28.08.2012 22:35, Michaël Michaud wrote:
>> Hi Matthias,
>>> now i remember me to the discussion and problems about the
>>> addMainMenuItem. Because i need my plugin runnable in actual versions, i
>>> try to look for an other way.
>> Just
On 28.08.2012 22:35, Michaël Michaud wrote:
> Hi Matthias,
>> now i remember me to the discussion and problems about the
>> addMainMenuItem. Because i need my plugin runnable in actual versions, i
>> try to look for an other way.
> Just curious. I wonder why back compatibility is so important
> for
Hi Matthias,
> now i remember me to the discussion and problems about the
> addMainMenuItem. Because i need my plugin runnable in actual versions, i
> try to look for an other way.
Just curious. I wonder why back compatibility is so important
for a software which is both cheap and easy to install (
Hi,
now i remember me to the discussion and problems about the
addMainMenuItem. Because i need my plugin runnable in actual versions, i
try to look for an other way.
But for the future i can made this changes in the FeatureInstaller class
in the same way as for the addMainMenuItem. Leave the ac
not sure if i understand correctly:
you want a checkable checkbox? or as in the layer status "editable" and
selectable, a checkmark shown that appear or disappears on re-click?
or am I thinking of the wrong menu?
cheers,
stefan
Am 20.08.12 15:56, schrieb Michaël Michaud:
> Hi Matthias,
>
> You
Right,
we actually ran in this issue before when the return type was changed and some
plugins stopped working because of the different method footprint.
that's why we added
addMainMenuPlugin() and deprecated addMainMenuItem()
as the only viable option seemed to use a different name, not elegan
Hi Matthias,
You're right and I can't see any solution without adding a new method,
or changing the accessibility of the third one from private to public.
I was tempted to say it is safe to change the return value from void to a
JMenuItem, but after I have read this article, I wouldn't recommend
Hi Ede,
i have to disappoint you. You mean the new addMainMenuItem methods, but
i talk about addPopupMenuItem. The addPopupMenuItem methods does not
return the menuitem at the moment :-(
Matthias
> the new addMenu methods of featureinstaller return the menuitem created. you
> can easily save t
the new addMenu methods of featureinstaller return the menuitem created. you
can easily save the reference and ask it on execute which state it is in.
regards ede
On 18.08.2012 18:58, Matthias Scholz wrote:
> Hi,
>
> i use the
>
> FeatureInstaller.addPopupMenuItem(JPopupMenu popupMenu, PlugIn ex
11 matches
Mail list logo
