Exporting text doesn't work outside of the editor. Here's how to reproduce:
Create a new Snap! project with the following code:
Try to save it to the cloud.
Now try to open that project to the community site.
Press the green flag.
→ Notice that nothing happens.
Try to press See Code
Press the green flag.
→ Notice that the text exports.
bh
April 4, 2024, 3:04am
2
Sigh. We don't support users using PRIMITIVE. Come back if there's a bug in the library that txt_export supports.
THEN WHY DO YOU LET THEM BE VISIBLE VIA A OPTION AT ALL!?
Users sometimes like to make their own libraries
Doesn't make sense with
because if they don't support users using PRIMITIVE, THEN WHY LET THEM BE VISIBLE AT ALL!? Libraries count.
No need to shout
The primitives were added to replace the use of the JavaScript reporter in the official libraries.
They are only designed to be used from those libraries.
They are hidden by default in the IDE but like most things in Snap!, we are allowed to look to see how things are done.
The libraries are supported but direct use of the primitives isn't.
sonic123cdmania:
Then either you or @bh explain this.
Uhh, no doesn't seem like it.
It follows from
Since they are only there to be used from the official libraries then it follows that they are not supported when used outside of them
Glad we've sorted out the confusion
bh
April 5, 2024, 12:51am
16
Geez. "We don't support X" means "we're not interested in bug reports about X." Not "if you do X we're going to come to your house and chop your hands off."
There's a setting to display them because (some of) the people who write libraries are users, not team members.
They are written to do the job needed by the library in question, not to generalize and bulletproof them to do anything a user might ask for.
Is that clear enough?
Geez, I never said you meant that! I just thought you meant "Never do X because only devs can do X, so users are never allowed to do X."
bh:
There's a setting to display them because (some of) the people who write libraries are users, not team members.
They are written to do the job needed by the library in question, not to generalize and bulletproof them to do anything a user might ask for.
Is that clear enough?
Yeah, that's clear enough for me. I guess I misunderstood.
bh
April 5, 2024, 7:07pm
18
Yeah I was exaggerating. ;~)
Maybe next time, PLEASE don't exaggerate?
bh
April 5, 2024, 7:45pm
20
Okay, if you'll refrain from yelling next time. ;~P