Legend overlapping with network nodes in term visualizations? How to resolve the overlap issues?

[junli1988]

Hi, this is probably a stupid question. But how do I prevent the legend from overlapping with random network nodes in the term visualization graphs? Is there a command that could enable me to fine-tune the term graphs? In this graph pasted below, the overlap is so bad that I can't even see the gene name. I'm still quite a noob to RStudio and this package. How did everyone else using this package resolve the issue? As much as I'd love to use the results from this package, this issue with term visualizations has made some of the graphs unable to be presented.

[egeulgen]

Hello,

Unfortunately, there is currently no way to prevent this overlap. I'll try and work on this, and update you if I manage to find a solution for this issue

[junli1988]

Hi Ege, thank you for the reply. If there's no way to prevent overlap, then is there a way to toggle the legend as "FALSE" so that it doesn't show up? Kind of like what we see in ggplot2 and ComplexHeatmap? I look forward to the updates on the package. Again, thanks for the help.

[egeulgen]

Just added the show_legend argument to visualize_term_interactions(), you can now toggle the legend to FALSE by setting this argument in either visualize_term_interactions() or visualize_terms().
To use this functionality, update to the latest development version (1.6.3.9008) via devtools.

[junli1988]

Thanks!

…

On Wed, Aug 24, 2022 at 2:41 PM Ege Ulgen ***@***.***> wrote: Just added the show_legend argument to visualize_term_interactions(), you can now toggle the legend to FALSE by setting this argument in either visualize_term_interactions() or visualize_terms(). To use this functionality, update to the latest development version (1.6.3.9008) via devtools. — Reply to this email directly, view it on GitHub <#141 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHEMDYP2A6ORAVMYKMTE3GDV2ZUFXANCNFSM57NAC2ZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>