• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Copy command executable in read-only mode

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 16869
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Copy command executable in read-only mode

blankman
blankman over 12 years ago

Hi, I notice in IC6 its possible to initiate the copy command in the layout editor even though the cellview is in read-only mode, whereas the stretch or move commands sound a warning when executed in read-only mode. I am finding this troublesome as when have copied a large array and go to paste, its results in having to cancel the command, excape out of the copy command, make the cell editable and start over. Is it possible to make the copy command non-executable in read-only mode?

Thanks

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    What precise subversion are you using? I can do Make Editable without it losing anything... (whether I pre-select or post-select in the copy).

    Of course the tool could be enhanced to prompt you to make it editable if the destination cellView (where you click to paste) was readonly (this would really need to be an enhancement CCR though), but I think that would be overkill - better just to figure out why the Make Editable approach is not working for you first (otherwise the exact same problem might occur when the tool itself does a make editable having prompted you).

    One situation I can imagine where it might discard  your select is when the data on disk is different from the readonly copy you have in memory. In that situation, doing a Make Editable does a refresh from disk (which it must, because otherwise you could clobber data carefully saved by the last person who edited the cellView) - and then any selection in memory would also have to be discarded because the objects in the original cellView have been discarded (even if the actual shapes which were selected are still in the same place when refreshed, the tool has no idea that they're actually the same shapes because the database objects get recreated). I just tried this and it does indeed throw away the selection in that case. Even if the tool prompted you during copy, you'd hit exactly the same problem.

    Perhaps that was your problem?

    In IC616 you will be able to use the yank and paste commands with pre-selection - so you can pre-select shapes, yank them (into a memory buffer) and then paste them - (a bit like a ctrl-C/ctrl-V combo in tools on Windows). A different paradigm, but that might solve your problem going forward.

    To prevent Copy altogether when readonly would need you to wrap the command in another function which checked if the cellView was readonly before you started - you'd then have to change your bindkeys (and probably the menus/toolbars if you cared that much) so that they called this new wrapper. Not sure it's worth it.

    Kind Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    What precise subversion are you using? I can do Make Editable without it losing anything... (whether I pre-select or post-select in the copy).

    Of course the tool could be enhanced to prompt you to make it editable if the destination cellView (where you click to paste) was readonly (this would really need to be an enhancement CCR though), but I think that would be overkill - better just to figure out why the Make Editable approach is not working for you first (otherwise the exact same problem might occur when the tool itself does a make editable having prompted you).

    One situation I can imagine where it might discard  your select is when the data on disk is different from the readonly copy you have in memory. In that situation, doing a Make Editable does a refresh from disk (which it must, because otherwise you could clobber data carefully saved by the last person who edited the cellView) - and then any selection in memory would also have to be discarded because the objects in the original cellView have been discarded (even if the actual shapes which were selected are still in the same place when refreshed, the tool has no idea that they're actually the same shapes because the database objects get recreated). I just tried this and it does indeed throw away the selection in that case. Even if the tool prompted you during copy, you'd hit exactly the same problem.

    Perhaps that was your problem?

    In IC616 you will be able to use the yank and paste commands with pre-selection - so you can pre-select shapes, yank them (into a memory buffer) and then paste them - (a bit like a ctrl-C/ctrl-V combo in tools on Windows). A different paradigm, but that might solve your problem going forward.

    To prevent Copy altogether when readonly would need you to wrap the command in another function which checked if the cellView was readonly before you started - you'd then have to change your bindkeys (and probably the menus/toolbars if you cared that much) so that they called this new wrapper. Not sure it's worth it.

    Kind Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information