-
vuice
2022-11-05 21:10:16 UTC this is definitely me when attempting to stickfigure
like why the actual fuck is the nodeCount edging the damn signed 32 bit integer limit, its literally a one-node stickfigure it should be 1 what is going on
all of the booleans are true on node_0 when they are supposed to be false
and whats with this e-notation bullshit, all the floating points are messed up except for node_0_Angle
why is my life coming to this
jHIjasjoi;dJAojidpoasogpoasdjoijad
Stick Nodes®
A stickfigure animation app created for mobile devices!
Create your own stickman animations on your Android or iOS device!
dude even the screenshots are betraying me thats so low-res
my attempt at a higher res screenshot, probably wont work
Alright, weather update, the booleans are now not fucked up
but everything else still bad and im trying to print as much shit into the console as I can about this
also does anyone know if the integer “2130706432” has any relation to anything, i tried looking it up and i got “invalid object” but i have zero clue what that means
haha its funny when it happens to someone else
please tell me that its supposed to be e-notation i want to be done soon
idk really, depends how you’re reading the data (or writing it wrong maybe)
all the other ints there are displayed properly (ver: 334 for example)
this is no different
Yeah, what’s bugging me is that the nodeCount is just a cumulation of all the “Number of child nodes” in the file that i decided to add to the dictionary for better accessibility, but in this case it was set to 2130706432 for virtually no reason
the figure in question is comprised of just the main node and the rounded segment
and the scale of the figure is 1.0, not 1.5 so i must have done something wrong there
as far as i know though, the 32-bit int translations arent buggy
If you’re trying to get a total node count from the file, there isn’t a total node count anywhere in the file.
The only node counts in the file are the numberOfChildNodes count as the last 4 bytes of every node to know whether it should iterate child nodes or move onto the next sister node.
The nodeCount is just the cumulation of every numberOfChildNodes,
it was used for a “while loop” , to loop a piece of code until the amount of times the loop occurs = nodeCount
but nodeCount is kind of wack right now for some reason and im trying to figure out why
The e notion for the floats are due to the odd nature of floating points.
Floating points basically use the binary equivalent of scientific notation, so it’s easy for floating points to represent a really really small number instead of 0.
For example, in your case representing something like 0.00000000 … 000000069 instead of 0.
Also, what are the allNodeIDs and node_x_Layer properties?
allNodeIDs is something I added to the dictionary to just add every node ID into a list
node_x_layer is just the draw order number (and ID), it was simpler to call it “layer” instead
I dont even remember why I added allNodeIDs, its probably time to remove it
One last thing. I think I messed up the documentation a little with colors. Each byte of the color (A,B,G, and R) may need to be unsigned so they range from 0 to 255 instead of -128 to 127
Ah, I already speculated that on my own, except for the alpha
Who is the warm toilet seat who programmed this ? 💢💢💢💢👿👿👿👿
me