UI Hint "REMEMBER_PREVIOUS_SELECTION" (FeatureScript)

Comments

• kevin_o_toole_1 Onshape Employees, Developers, HDM Posts: 565

  May 2017

  I don't know your precise use case, but if you have a situation where you have multiple features needing to reference the same entities, perhaps a good workflow would be to have a setup "Start" feature which flags the necessary entities by setting context variables or entity attributes, and then successive features reference those entities.
  
  Alternatively, you can do it without making another feature by using editing logic: Remember the values of the previous feature in with context variables or attributes, then, using editing logic on feature creation, set the parameter value to the query you find, if any.
  
  
  
  To clarify a bit on why the obvious thing doesn't do the job: REMEMBER_PREVIOUS_VALUE works for almost all parameter types, but not Queries. That remembered value is associated the user (not the tab or the document), so when you're working in another Part Studio tomorrow, that previous value will still be remembered. This usually doesn't make sense for selections, which tend to have transient scope (they're nonsensical outside the single Part Studio, and even within the Part Studio they may not exist earlier or later in feature history). The workaround above gets around this by confining the scope to the current Part Studio, and performing an evaluation in the editing logic function to check if queried entity still exists.
  
  

  0
• darren_13 Member, Developers Posts: 119 PRO

  May 2017

  @kevin_o_toole_1, the editing logic sound very much like what I need. I'll have a play with this and let you know how it goes. 
  
  Thank you very much for your help,
  Darren

  0
• ben_partouch Member, csevp Posts: 134 PRO

  November 21

  @darren_13 ,

  Did you manage to get this to work? I have the same scenario.

  Thank you

  0
• EvanReese Member, Mentor Posts: 2,135 ✭✭✭✭✭

  November 22 edited November 22

  Here's an example of a way to do it. I commented thought process in the code, but let me know if you have questions. Perhaps someone could write it more concisely than me, but this works.

  

  Evan Reese
  

  0