Chris, Sorry for the late reply. To answer your question, please go ahead and make these changes. I've had them in my todo list forever and I'm not making any headway so I will gladly pass the baton to you. I do have a few concerns.
1. There is currently no cut/copy and paste support in pcbnew at least in the traditional sense. This is something we can look at after the stable release as I have certain direction that I want to go with this so please don't make any changes to the pcbnew copy/cut and paste at this time. 2. Be very careful when pasting blocks with sheets in hierarchical schematics in Eeschema. Historically this has been (and maybe still is) problematic. Do lots of testing in this regard. 3. Please use the standard Ctrl-C, Ctrl-X, and Ctrl-V key bindings. Reassign any hotkey conflicts as required. To cut down on the grumbling, you might want to get some feedback from other developers and users as to what hotkey to assign to the conflicts. In any event you have my permission to use the standard key bindings. We should have never allowed those hotkeys to be used for anything else by default. 3. Please update the documentation accordingly if at all possible. If not, try to get some help. Perhaps the documentation folks would be willing to help you. You can clone the current documentation from https://github.com/ciampix/kicad-doc and make a pull request with any changes. At some point in the not too distant future, the asciidoc part of this repo will become the "offical" kicad documentation. Thanks, Wayne On 3/21/2015 11:48 AM, Chris Pavlina wrote: > Relatively simple proposals: > > 1. Rename 'copy' to 'duplicate' in eeschema to match pcbnew. > 2. Rename 'save' to 'copy' in eeschema to match traditional usage. > 3. Add default Ctrl-V keybinding to eeschema for 'paste' to match > traditional usage. > 4. Add 'cut' to eeschema, on Ctrl-X: > - This differs from save/copy->delete in that it should keep > reference designators, since you're just moving parts. > - This differs from block-move in that it would work across sheets, > which I think is a significant plus. > > Possible drawbacks: > > 1. Existing tutorials/unofficial docs will not match. Not such a big > deal in this case as 'duplicate' is quite obvious. > 2. Existing tutorials/unofficial docs will not match. Bit more important > for save vs. copy. > 3. Keybinding conflict with pcbnew's Add MicroVia, so pcbnew couldn't be > amended to add this keybinding to *it* for > consistency. There's always the possibility that Add MicroVia could > be given a different binding, as I don't > think it's a very often used function. > 4. None that I can think of. > > Any thoughts on this? These are all things I can easily implement if > desired. > > Chris > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
