Sunburned Surveyor wrote: > Thank you for the responses Martin and Stefan. I need to clear up one thing: > > Martin wrote: " I think actually that OJ will copy any source Feature > attributes which match the destination schema in name and type (which of > course includes the Geometry attribute)." > > If this is true, why is a second replicate function needed, as Stefan > mentioned? Wouldn't the one function do it all? > I dunno. Probably I'm out of touch with what the code does. You really need to dig into the code and find out how it works - otherwise you're liable to replicate functionality which is already there. And you always learn a lot by reading code.... > I'll do some more testing to confirm the feature copying and pasting > behavior and I will report back to the list with what I find. > > Thanks Again, > > The Sunburned Surveyor > > > > On 9/13/07, Stefan Steiniger <[EMAIL PROTECTED]> wrote: > >> see below >> >> Martin Davis schrieb: >> >>> Sunburned Surveyor wrote: >>> >>>> - OpenJUMP creates "new" features in the destination layer with new FIDs. >>>> - OpenJUMP only pastes the Feature gemetries, and not the other >>>> Feature attributes. (This makes sense, as you avoid having to check >>>> for FeatureSchema conflicts.) >>>> >>>> >>> More or less. I think actually that OJ will copy any source Feature >>> attributes which match the destination schema in name and type (which of >>> course includes the Geometry attribute). >>> >> we have also a second function (replicate) that copies not only >> geometries (which the original function does in every case) but also >> attributes if no FeatureSchema conflicts appear >> >> >>>> Can anyone confirm that these statements are correct? >>>> >>>> Can anyone quickly tell me which class contains the method that >>>> performs the copy and paste? I'd like to "steal" this logic for my >>>> send to button, instead of reinventing the wheel. >>>> >>>> >>> Not sure.... but it shouldn't be too hard to find. Start at the Paste >>> Feature button code and drill down from there. >>> >> yes.. look for the naming "string".. then you will find the code >> >>>> Thanks, >>>> >>>> The Sunburned Surveyor >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.net email is sponsored by: Microsoft >>>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> _______________________________________________ >>>> Jump-pilot-devel mailing list >>>> Jump-pilot-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>> >>>> >>>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >
-- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
