@yitong@notdetails@figma@autoflowplugin i don't believe there is a way of avoiding the O(N) upfront cost of checking coordinates of every child of the parent node in question
there are optimizations (e.g. interval tree) for performing repeated operations on the same document state, but as for constructing the tree π€·ββοΈ
I'm speaking at @figmadesign's Config this Thursday about the principles behind designing for Machine Learning! π§
You can register (for free) here: https://t.co/woi2YwwTu9
#Config2021
@s2tephen@yitong it should! anything funky that you're running into?
the only cases where it won't draw should be when 1) your src/dst nodes have an ancestor/descendant relationship or 2) there are no non-overlapping paths between any pair of the 4 cardinal midpoints
Georgia is just brute forcing this thing over the line. Not a pretty split, but a <10k lead is pretty amazing. This is the 4:55 PM update.
https://t.co/cN5IFdVB73
If Texas flips
1) Huge ups to @BetoORourke for getting out the vote the past few years
2) Living through every sweaty Houston summer as a kid will have been worth it
@michlimlim Apart from pre-quarantine nostalgia for travel & driving, 2 things SWEs do a lot of, it's a rare side project created not in pursuit of profit, nor utility, nor self-improvement, but understated delight thatΒ demands nothing of anyone. It also reminds me of playing GTA
i don't have respect for any cuisine that doesn't use anchovies like this stuff is so good and all over the sea how could you possibly leave this much flavour on / off the table
@skuwamoto@p44v9n@yitong@autoflowplugin Yes, we've noticed that the stroke cap will disappear when it's located on a vector segment connected to a turn/angle, and the segment shrinks beyond a certain point. The smaller the corner radius, the smaller the segment it takes to trigger the disappearing: