search

chkunkel / projection_viewer

An interactive viewer
13 stars 1 forks source link

text box with parameters covers the graph #21

Open stenczelt opened 4 years ago

stenczelt commented 4 years ago

raised in: https://github.com/libAtoms/abcd/issues/88#issue-580729012 by eszter137

When moving the cursor over a structure on the graph, the parameters of the point will cover the graph. (Maybe it's only when having many keys in the database.) Would it be possible to put it somewhere above/below the graph?

Yap, there was in idea to limit the number of lines in those boxes, but not implemented yet. The hover info is a builtin thing of plotly, I am not sure how to have that below it in a simple way other than having a new box and implementing all the logic to put it there. Originally posted by @stenczelt in https://github.com/libAtoms/abcd/issues/88#issuecomment-599513334

gabor1 commented 4 years ago

I actually quite like all that info, but I agree that it can be obscuring. It would be nice if Plotly can just be told (or hacked) to offset it vertically by some (large) distance to that it is below the plot.

-- Gábor

Gábor Csányi Professor of Molecular Modelling Engineering Laboratory, University of Cambridge Pembroke College Cambridge

Pembroke College supports CARA. A Lifeline to Academics at Risk. http://www.cara.ngo/

On 16 Mar 2020, at 12:44, Tamas Stenczel notifications@github.com wrote:

raised in: libAtoms/abcd#88 (comment) by eszter137

When moving the cursor over a structure on the graph, the parameters of the point will cover the graph. (Maybe it's only when having many keys in the database.) Would it be possible to put it somewhere above/below the graph?

Yap, there was in idea to limit the number of lines in those boxes, but not implemented yet. The hover info is a builtin thing of plotly, I am not sure how to have that below it in a simple way other than having a new box and implementing all the logic to put it there. Originally posted by @stenczelt in libAtoms/abcd#88 (comment)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.