Skip to content

Conversation

@nilscb
Copy link
Collaborator

@nilscb nilscb commented Nov 24, 2025

…yers #2320"

@nilscb nilscb self-assigned this Nov 24, 2025
@nilscb nilscb added bug Something isn't working AspenTech Task owned by AspenTech labels Nov 24, 2025
@nilscb nilscb linked an issue Nov 24, 2025 that may be closed by this pull request
coords,
showReadout = coords?.visible ?? true,
pickingDepth = coords?.pickDepth ?? 2,
pickingDepth = coords?.pickDepth ?? 5,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why changing the default value ?
Does it really fix anything ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No this doesn't fix anything. 2 is barely mutlipicking. 10 is the default from deck.gl. It can affect performance if set to high. Of course its only a defaul value. I dont have any strong feelings about it.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I remember you did set to 2 for performance reason.
If there is no impact on this PR, reset it to 2 please.

return [0, 0, 0];
}

decodePickingColor(/*color: Uint8Array*/): number {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this used ? If not, remove it

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Used by deck,gl to in this case map all colors to index zero. (As this layer does not have multiple index's)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add that in a comment, please.

@nilscb
Copy link
Collaborator Author

nilscb commented Nov 25, 2025

Note. I may have to do this fix also for other non standard layers but prefer to do this in a separate PR

@nilscb nilscb requested a review from w1nklr November 25, 2025 09:24
@nilscb nilscb requested a review from hkfb November 26, 2025 06:59
return [0, 0, 0];
}

decodePickingColor(/*color: Uint8Array*/): number {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add that in a comment, please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AspenTech Task owned by AspenTech bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SubsurfaceViewer: pickingRadius not working with overlapping layers

2 participants