David Sehnal

You can try giving it `position: fixed; z-index: 1000000` or something along these lines.

You need to wrap this in `atoms` query (and use say the `chain` aggregation) which provides the "current element location" to the callback. Basically you are filtering just elements that...

The easiest way would likely be subtracting the atom in question from the corresponding "structure component". Search the codebase for `modifyByCurrentSelection` [link](https://github.com/molstar/molstar/blob/master/src/mol-plugin-state/manager/structure/component.ts#L202) Before: After:

- I think the on/off could also use a label in front of it. - Or perhaps you can also use `MappedStatic` parameter type where you name the options an...

Yes, this is definitely currently unsupported behavior.

@arose ok to merge this?

Hi Julia, your code looks more like a plugin spec rather than creating a state. Is using mol* an option for you?

You are right, the typing indeed seems to be wrong here. I've adjusted the type in #1048. Btw there is also a Python BinaryCIF encoder implemented here https://github.com/molstar/ciftools-python

This code was written by @arose, but adjusting the `contextHash` value based on the current trajectory snapshots in your custom theme should fix your issue.

It is possible but currently isn't available "out of the box". It requires defining custom visuals that represent the interactions.