kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

This makes more sense.  I can see value in being able to copy/paste this
way.

On 1/18/2018 8:23 AM, Kristoffer Ödmark wrote:
> I do see the value of copy pasting between schematics. Its very common
> for design reuse.
> 
> The way the copy-paste for pcbnew is done is like this:
> 
> Copy:
> 1. checks what items are selected.
> 2. check what requirements the selected items have( nets, layers etc)
> 3. this creates a new pcb file in memory with only the selected items (
> using the regular parser)
> 4. instead of writing the pcb file to disk, it is written as plaintext
> to the clipboard.
> 
> Paste:
> 1. load the pcb file from clipboard as a regular pcb_file ( using the
> regular parser )
> 2. check what new nets layers etc are present in the file and add to
> current working pcb.
> 3. add each item to the pcb and to selection.
> 4. enter "move" mode for the current selection of items.
> 
> Maybe something similar can be done for the schematic, although I was
> lucky, because a lot of the functionality was already in pcbnew, so I
> only had to connect most of it in a more streamlined way.
> 
> 
> The current way I copy paste between schematics is like this:
> 1. create new hierarchical schematic.
> 2. copy block ( ctrl+c )
> 3. enter new hierarchical schematic and paste there. save.
> 4. remove the hierarchical schematic from project.
> 
> Now you have your selection in the new scheet file, and can move it
> wherever you want. Not the most elegant solution, but since I usually
> create as much I can as "schematic modules" I have a small collection of
> schematics i add to a project to get the stuff I usually have.
> 
> With the work being done on improving the bus things in eeschema, I cant
> wait to improve my modules!
> 
>  -Kristoffer
> 
> On 01/18/2018 01:53 PM, Wayne Stambaugh wrote:
>> Hi Badr,
>>
>> As far as I know, no one is working on this.  We still have a lot of
>> work to do just to get a full copy/paste implementation for each editor.
>>   I'm not sure copy/paste between eeschema applications has a lot of
>> value but there could be some overlap for graphical objects.  Copying a
>> pin from the symbol editor and pasting it in the schematic editor has no
>> meaning since pins are not schematic objects.  Pins are symbol objects
>> and only have meaning in library symbol objects.  Copy/paste between the
>> to editors will not be trivial to implement.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 1/17/2018 4:55 PM, Badr Hack&Invent wrote:
>>> Hi,
>>> I'd like to add the possibility to make a copy/paste of a block between
>>> two different eeschema applications, or either to export a selected
>>> block to a new .sch file.
>>> Any idea if it is ongoing by someone, or a hint from where to start?
>>> Thank you in advance,
>>> Regards,
>>> Badr
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp