Hilaire,
as soon as the hash of an object changes because you change an attribute
that is used in the hash function, the object is not identical to its
older ego any more, so Voyage cannot know it still is the same object
(nor any other caching solution).
Or am I wrong about this whole hash/= thing?
The only thing I could imagine is that Voyage somewhere uses = where it
should use ==. But wouldn't many more people have problems then?
Joachim
Am 06.03.17 um 18:03 schrieb Hilaire:
The more I think the more it seems wrong to me. Whenever you ask an
instance to save itself, if already in repo it should not duplicate
itself whenever hash/= is overrided in this object. It does not sound as
an expected behaviour.
Hilaire
Le 05/03/2017 à 14:51, Hilaire a écrit :
Understood.
My use/understanding of hash and =, true in DrGeo, was more like unique
identifier regarding its ontological characteristics (what distinguish
it from other). So an exact same Point in DrGeo will have different hash
value depending on its position on the plane, or it being free on a
line, etc. May be I got it biased here.
Anyway problem solved, comparing protocol was just rampant code.
--
-----------------------------------------------------------------------
Objektfabrik Joachim Tuchel mailto:jtuc...@objektfabrik.de
Fliederweg 1 http://www.objektfabrik.de
D-71640 Ludwigsburg http://joachimtuchel.wordpress.com
Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1
