Alice Averlong🏳️⚧️ugh. the good news is that I can write some clever xpath that makes this SVG-manipulation trivial
the bad news is that I'm having to use ElementTree, which has "limited support for XPath expressions", so NOPE! my xpath won't work
it has been zero days since I crashed fusion360
ooh it's repeatable. that's fun
currently engaging in crash-oriented programming. the docs are incomplete and unclear, so I'm trying different things and seeing if they crash, work, or give me an error
one part of the python API for Fusion 360 is undocumented and just assumes you recognize that it's backed by a certain C++ object and that you know how STL std::vector's work
well I can do it one way, which crashes, and another way, which silently does nothing.
quality software and/or documentation
well I searched the docs for the function that's failing, and got two result:
the lying docs
and a forum post from 4 months ago saying that the function may have a bug that makes it not work
no replies
the lying docs
and a forum post from 4 months ago saying that the function may have a bug that makes it not work
no replies
ahh, I figured out it was generating the wrong kind of operation. so I switched it to the correct operation!
and it still crashes
I'm assigning an array to another array, and it's throwing a null pointer error in Iron::CadCurvesBase::setInputs. Weird.
I am trying SO HARD to not open ghidra right now
I have apparently crashed fusion360 so hard that it won't open again. uh-oh
oh my god
it WAS ghidra!
I didn't even try to open fusion360 in ghidra, but I had ghidra running in the background for my duke nukem project.
when I closed ghidra, fusion360 finally opened
it WAS ghidra!
I didn't even try to open fusion360 in ghidra, but I had ghidra running in the background for my duke nukem project.
when I closed ghidra, fusion360 finally opened
and I crashed it again
good news!
it didn't crash.
it instead hung.
welcome to the future:
where even your CAD program is actually chrome
where even your CAD program is actually chrome
I'm looking at screenshots from July and they're not matching my current program
and I can't tell if something has gone wrong or if they've updated the program in the background
and I can't tell if something has gone wrong or if they've updated the program in the background
it could easily be both
fusion360 is the king of code that looks like it contains obvious typos but doesn't:
op.parameters.itemByName('tool_coolant').value.value = "'disabled'"
that last bit is a little easier to see if you have your mastodon set to a monospaced font but who would do such a thing?
even better, it turns out this code DOES contain a bug!
despite the saved templates storing the value as "'disabled'" (that's double-quote-single-quote-disabled-single-quote-doublequote) and the list of values clearly saying single-quote-disabled-single-quote, and you assigning a value, not a name... it wants no single quotes.
the name would be Disabled, btw, but apparently the correct value is disabled, no quotes.
fusion360 interprets programmers trying to use their API/docs as damage and routes around them
Serophos@foone that gave me a headache 😂
slaeshjag@foone @slaeshjag yep, bitlbee through irssi
Jernej Simončič �@foone Your instance doesn't support
markdown for inline code blocks?@jernej__s if it does, I have no idea how to activate it.
@foone For me it's on by default, but can be changed to plain text or HTML in the toolbar below the text entry box: