Hi All,
I am a new user to the open jump tool, i had a doubt regarding the area
feature implemented in the tool. when ever i drag and drop the mouse and
select a portion in the map i see the values of distance and the area
displayed in the tool bar,but sometimes the area value calculated seems to
If we are concerned about memory we might try a single int as a
counter instead of using an int to count mods for each attribute. So
you could do something like this:
// Private member variable to count attribute modifications.
private int attModCounter = 0;
public void setAttribute()
{
// Do
>
> But there's something that could go wrong anyway, because an attribute
> has a NULL value by default and client code may decide to not set
> attributes at all if it has no value to set them to. If this happens,
> the Feature could remain not-modified for ever.
>
This is possible, but not likel
>
> Perhaps you could extend BasicFeature to be a MutableBasicFeature, and
> this is the concrete class that would be used by Writeable DataStores.
>
This is a good idea, but tough to implement. A search for "new
BasicFeature" found 80 matches in the project. The fact is that most tools
create B
Hi Michaël,
We need to track modifications on a per-feature basis because it is
> necessary to update a database source when a modification is done in the
> OJ UI : right/wrong
Right.
You propose to track modification on each attribute individually because
> you don't want to update a whole dat
Maybe it would be possibile to add explicit init methods like:
beginInit()
endInit()
or even a single "atomic" method:
init(Object[])
So that mod-aware calling code could call them to let the Feature "know"
it is being initialized.
Still the Feature could manage a disposa
