Behavior of SelectionCommandInput

Behavior of SelectionCommandInput

Anonymous
Not applicable
356 Views
1 Reply
Message 1 of 2

Behavior of SelectionCommandInput

Anonymous
Not applicable

I'm confused about the way the SelectionCommandInput works.

 

With the selectionLimits are set to single-select, you can start your selection with an object (eg. occurrence) in the browser or in the viewport. If you then want to select another object, you can select the object in the viewport but not in the browser.

 

I don´t have to post my code here because you can try it on the UI command "New component". You can change the selection for "parent" by clicking on objects in the viewport but not in the browser.

 

new component.PNG

 

Is this "as designed"?

 

Edit/Addendum: same problem described here (no solution)change-select-by-mouse

single-select (limits 1,1) => no selection in browser

multi-select (limits 0,0) => selection in browser

0 Likes
357 Views
1 Reply
Reply (1)
Message 2 of 2

MichaelT_123
Advisor
Advisor

Hi Mr.Steinbach,

 

If the issue is real I would live with it ... unless others are fixed.

Nevertheless, one must recognize that selection pallets in Browser and ViewPort are different. They overlap but are limited to their abilities. Additionally, SelectionFilters play their contextual role too.

I checked what you described and when UI selection filter pallet is limited to Components only  (I have not checked other combinations as there are too many )  and everything went smoothly. Have Developers360 omitted an entity type filter? 

 

Concerning your code, consider checking :  SelectionInput.addSelectionFilter('what')

 

Regards

MichaelT

 

 

MichaelT
0 Likes