Stats

  • Locked Locked
  • Replies 19
  • Subscribers 143
  • Views 18343
  • 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

Reselect Items

blankman

Hi all, is it possible in skill to create a reselect tool, that would reselect any preselected number of objects in the event of deselecting by mistake? For instance, when doing complex stretches that involve carefully selecting only certain objects, it can be quite cumbersome when one looses the selection and has to go to the trouble of reselecting everything again. Thanks,

Brian.
Parents

  • Brian,

    That checking is not what I meant. That adds checks to ensure that all the objects still exist - which isn't really necessary, and indeed makes this less useful. The whole point of storing it in a group is that if an object is deleted, the corresponding groupMember goes too - so  deleting a shape or instance which was in your stored selected set will cause it to be removed from the stored group automatically.

    So the whole BSgroupLength1 and BSgroupPoints1 stuff is unnecessary. With this check, it will stop you being able to use the selection save/restore if any of the members are deleted - and in fact it would have behaved sensibly. The check that I'd omitted was ensuring that the partialSelect information may have a different number of points in it  than the shape it's referring to - the shape (if it was a polygon or a path) may have been edited so it now has a different number of points. It will only be an issue for polygons and paths, since these are the only shape types (I think) which can alter the number of points (in IC5141 at least; in IC61 this is superseded by the built-in capability to save/restore the selection set). So you may need to check groupMem~>object~>objType to see if it's a path or polygon, and then compare groupMem~>object~>nPoints with length(partialSelect).

    Regards,

    Andrew.

Reply

  • Brian,

    That checking is not what I meant. That adds checks to ensure that all the objects still exist - which isn't really necessary, and indeed makes this less useful. The whole point of storing it in a group is that if an object is deleted, the corresponding groupMember goes too - so  deleting a shape or instance which was in your stored selected set will cause it to be removed from the stored group automatically.

    So the whole BSgroupLength1 and BSgroupPoints1 stuff is unnecessary. With this check, it will stop you being able to use the selection save/restore if any of the members are deleted - and in fact it would have behaved sensibly. The check that I'd omitted was ensuring that the partialSelect information may have a different number of points in it  than the shape it's referring to - the shape (if it was a polygon or a path) may have been edited so it now has a different number of points. It will only be an issue for polygons and paths, since these are the only shape types (I think) which can alter the number of points (in IC5141 at least; in IC61 this is superseded by the built-in capability to save/restore the selection set). So you may need to check groupMem~>object~>objType to see if it's a path or polygon, and then compare groupMem~>object~>nPoints with length(partialSelect).

    Regards,

    Andrew.

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.