You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, some of the functions (such as mplhep.lhcb.text) take a loc keyword that has to be a number, hardcoded. For the LHCb-style, these are all left-aligned.
How should new locations be added? Or is there the possibility to specify an arbitrary location?
The text was updated successfully, but these errors were encountered:
When you say "adding another number", do you mean to hardcode it inside the plotting function? That means there is no way for a user to choose an arbitrary location? I .e. could loc allow for, say, a tuple of x, y coords? Or something else, more mpl standardized maybe?
Oh, I see. I think I misunderstood. I'd be ok with making loc also take an (x,y) tuples. The initial idea here was to offer a set of predefined locations that are commonly used and hard-code them to prevent the situation where eg every "CMS Simulation" label had a slightly different size ratio, a slightly different gap between words, or different spacing from the label to the x and y-axis. I assumed that's close to 100% of use cases, but if not I have no problem with that being extended.
Currently, some of the functions (such as
mplhep.lhcb.text
) take aloc
keyword that has to be a number, hardcoded. For the LHCb-style, these are all left-aligned.How should new locations be added? Or is there the possibility to specify an arbitrary location?
The text was updated successfully, but these errors were encountered: