Owen Lynch
Owen Lynch
In relation to all this, I had a thought when I was walking today. It is useful to have persistent names for elements of an acset for defining functions in/out...
Yeah, that's what I was thinking. There are other glitches that I've seen, and so I think this will fix *something*.
Yes, this is a feature not a bug; I want to explicitly control my conda environments. I'd consider adding this as an option if you send a PR.
Actually, running this on my computer, I'm getting a bunch of warnings about things not being able to be checked at runtime: ``` [warn] -- Warning: /home/o/g/AlgebraicJulia/Semagrams.jl/scala/core/src/graphs/sprites/Arrow.scala:8:41 [warn] 8 |import...
OK, I'm also noticing that the ```scala case Event.MouseLeave(backgrounPart) => IO(Some(())) ``` branch of the match statement in `MoveViaDrag` is firing when I leave the box part. So perhaps something...
Another regression; you don't make the arrow unhoverable while you drag, so it intercepts the hover event that you want to send to the thing you are dragging the arrow...
There are also a ton of `println`s everywhere...
OK, in general the whole "one part for two things" stuff that's going on for Homs in the acset editor is *super* buggy. I don't really know how it is...
> > OK, I'm also noticing that the > > ```scala > > case Event.MouseLeave(backgrounPart) => IO(Some(())) > > ``` > > > > > > > > > >...
Thanks @sjbreiner!