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
I would expect from here that such input should be handled.
A workaround would be to substitute rot = $(gp.elabels_rotation) with something like rot = Vector{Float32}(fill($(gp.elabels_rotation), ne(gp.graph[])). This would also encourage to have elabels_opposite being applied to all input elabels_rotation rather just give out a fixed rotation based on the vertices position, as mentioned on #67
Passing in elabels_opposite will not influence the result. In my opinion this shouldn't be the case and I would propose to move the relative for loop outside the if-else statement. But this would mean that the "opposite" applies to the rotations handled in and it doesn't give out a particular opposite angle as it is now.
From the other side maybe using Vector{Float32} is not very generic ?
The text was updated successfully, but these errors were encountered:
Would be interesting to see if this worked on Makie v0.15. I am pretty sure I've tested this before 🤔
However, this is just another hint that we really need to get some reference testing going #22
I would expect from here that such input should be handled.
A workaround would be to substitute
rot = $(gp.elabels_rotation)
with something likerot = Vector{Float32}(fill($(gp.elabels_rotation), ne(gp.graph[]))
. This would also encourage to haveelabels_opposite
being applied to all input elabels_rotation rather just give out a fixed rotation based on the vertices position, as mentioned on #67From the other side maybe using
Vector{Float32}
is not very generic ?The text was updated successfully, but these errors were encountered: