Hi Carsten,
Carsten Neumann wrote:
>
> I'm not convinced this is a good idea. For example, how would this
> affect tutorials that use the SSM and clustering ? Also the SSM
> (although never intended for things much larger than the tutorials) is
> quite widely used (this is my impression from this mailing lists posts),
> so it's quite possible this change breaks somebodies app by clearing the
> changelist behind their back.
Agreed.
> Putting the commitChangesAndClear call into the tutorials display
> callback sounds like the right approach to make users aware of this.
Yup.
> On the other hand, 1.x does not really need it, since changelists have
> to be made explicitly read/writable - maybe this should be ported to 2
> and the whole issue would resolve ?
Hm, I don't think we can do that in 2, as we need to know what changed in
commitChanges(). In 1 endEdit took care of that, but that's disappeared.
The real solution is making people aware of the need to call commitChanges()
(which they have to do anyway), and add those to the tuts at the right points.
Dirk
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
