A confusing wrinkle I tripped over while prototyping a new card: links in rtext cannot be other fonts than "body" except when within a field widget where the widget font property is set to something other than default.

I was very confused by this because RevInc was full of links with custom fonts, so when I was testing out some code involving the "link" event, I was surprised to find that highlighting one of the links to change the font also lost the link. Trying a different tack, I tried changing the font first, then selecting and adding a link ... and that switched the selection font to "body". If you try to brute force it from a script by calling rtext.make with both a custom font and a link argument, you get the even more confusing result of it ignoring the font argument but also not making a link, so you just get a string in "body" font. 

Only by setting the Font property of the widget to some other font can I then make links in that font, but only in that font. I presume this is because the Font property overrides "body" being the default font. RevInc used this a bunch, which is why I didn't realize it acted differently otherwise.

This also seems to have consequences for prototypes/contraptions with rtext attributes, because the form field in the properties dialogue obeys the default behavior, with "body" as the default font. I'm not sure it's even possible to override in that case, though I haven't really tested it. I know it doesn't work with Millie's colourText contraption, not that it matters anyway because of the way it works by drawing text fields to a canvas.