Hi, > layerview context menu. OK, let's go this way, >> I think we should have a general policy for that. > possibly yeah. but there is nobody to enforce it anyway, even if we had it ;) As I'm a lazy programmer (as we probably all are) when I add a new feature, I tend to start from a feature which is close enough and to adapt it, not from the best (or most uptodate) one. That's where a document (or wiki page) describing the best practises and improved year after year would be helpful.
> if i had to implement it, i'd do similar to the geometry converter Could you be more precise, or remind me how converter is different from other plugins ? > i did a handy UndoableSetGeometry class for geomconv, which could be easily > put into plugin's which edit geometries and that are currently not undoable Must have a new look at it. Undo/Redo management in OJ has always been a pain for me. Michaël > >> Hey, seems we'll never be bored. >> > exactly my point.. ede > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
