onChangeSelection() not triggered in frame5

[digital mantle]

I have a question that may very well be a bug or just a feature I don't understand fully: say I have two frame5s, each with an onChangeSelection link tag. If the frames are docked separately they both trigger properly, but if you superimpose one to the other (see attached image) only the currently focused frame will trigger the event.

I'm sure there is an easy workaround that can be achieved to update both frames (eg having the mtscript that's called call the other update as well), but, this doesn't seem like the intended behavior and I thought it was worth mentioning here.

[molten spire]

This is definitely worth filing a bug report/issue on GitHub. Good catch, btw. 👍

[hard vale]

I do know for the event to trigger the frame has to be visible and on top. This has always been the case. You can't have it tabbed or pinned and collapsed.

[teal sparrow]

Just so I don't get confused though, you could use an overlay or one oCS event to check / trigger the update (e.g. if oCS event A is triggered, could that not run a macro to update the minimized frame)?

[molten spire]

Hm. I don't see a reason why that would be the case.

[digital mantle]

With it pinned and collapsed it seems to work just fine fyi

[digital mantle]

Will try to. Since i only play at programming I'm not even sure I have a github account (i know, shameful)

[digital mantle]

Yes, if you use the same function for both oCS events to update both it works just fine, which is what I ended up doing, but since I thought the behavior was odd I thought it best to bring up.

Apparently i did have an account. Bug report submitted 🙌