InteractiveComplexHeatmap icon indicating copy to clipboard operation
InteractiveComplexHeatmap copied to clipboard

Wrong sub-heatmap selection

Open Keragen opened this issue 9 months ago • 4 comments

Image

Hello, when I select rows from the main heatmap, I don't get the right row names in the sub heatmap. It looks like the selection is shifted down by 9 rows (see picture). Also, It only occurs when I run my app in shinyproxy. from R studio I don't have this bug. Do you have any idea about what causes the problem and how to solve it? Thank you!

Keragen avatar Apr 25 '25 12:04 Keragen

Hi @Keragen,

interesting finding, I was immediately afraid that this could be the cause for my via ShinyProxy deployed R Shiny application as well 😅 But luckily for mine it seems to work (see below)

Image

Maybe that trying to reproduce it could at least help to show you that this does not seem to be a general issue of ShinyProxy deployed R Shiny applications leveraging InteractIveComplexHeatmap,

One random idea 💭 : Maybe it could be related to the heatmap size, since the one on the screenshot seems to be quite large. Have you tried already if that bug appears when you have a smaller heatmap?

Good luck 🤞 with debugging your application looks already quite promising 🚀

IvoLeist avatar Apr 27 '25 10:04 IvoLeist

Hello and thanks for the answer. It seems to be related to the plot resolution (and not the amount of data). The greater the height the bigger the shift. What is puzzling is it works at every resolution on my windows R studio. (the faulty shinyproxy version runs on a ubuntu server, same code, same R version).

Keragen avatar Apr 29 '25 12:04 Keragen

Ok, I found what causes it. The bug occurs when I zoom out with google chrome (ctrl+mouse wheel). when I zoom in (>=100%) it is fine. It only happens with shiny proxy though, so I guess the problem is between shiny proxy and chrome and not with InteractiveComplexHeatmap. Let's call this problem solved for the moment. Thanks again for the input @IvoLeist !

Keragen avatar May 06 '25 14:05 Keragen

Cool that you managed to pin point when exactly that bug is happening.

Just out of curiosity I tried if my application shows the same behavior but so far I have not managed to reproduce it.

Here are my relevant versions:

IvoLeist avatar May 06 '25 19:05 IvoLeist