Feature Proposal: Support clicking [url] tag

[CharlieDelune]

By default, godot's RichTextLabel has pretty good support for the [url] bbcode tag. If you wrap some text in the url tag, such as
Hey, [url]what's[/url] up?
When you click on the word "what's" specifically, the RichTextLabel will emit the meta_clicked value with a value what's.
This can be further extended by setting a specific value.
Hey, [url={"some": "json"}]what's[/url] up?
In that case the value of the meta_clicked signal will be {"some": "json"} instead of the word that was clicked.

This behaviour is documented in godot's documentation for RichTextLabel in the meta_clicked signal section: https://docs.godotengine.org/en/stable/classes/class_richtextlabel.html

This is an extremely useful way of handling clicks on single words within a dialogue.

I would love to have a way of doing this with GDM

[CharlieDelune]

I'm going to close this because I now see that this feature is probably supported entirely, just not in the example.

[Iakobs]

Hi, I'm interested in this because how do you handle the meta clicked of the DialogueLabel before the click event is processed by the parent node DialogueBalloon, which consumes the click event to go to the next line of dialogue? What I mean is that the meta_clicked event is never processed because the parent node consumes the event before.

[CharlieDelune]

@Iakobs Yeah, unfortunately this ended up being a really complex scenario. The RichTextLabel in the dialogue balloon is set to ignore, I believe, which means the UI won't handle any clicks on the text. If you set the label to stop mouse propagation, you'll start getting your clicks on url tags handled, but then clicking on any of the text prevents the dialogue from advancing. It was pretty terrible behaviour.

What I ended up doing initially was to put a GridContainer into the dialogue balloon, and then I would create a new RichTextLabel for every word in the dialogue and added it to the GridContainer. This didn't look any different from the normal dialogue, but it allowed me to set the mouse propagation for words I want to be clickable to Stop, and all of the other ones to Ignore.

It worked, and it worked well enough...

But ultimately I kept finding things that I wanted to do with my dialogue system that using this library didn't support, so I ended up abandoning the library all together, spent a week writing my own, and now it does all the thing I require from it.

[Iakobs]

Yes, I understand that. I'm facing a similar problem, but I've just found another solution which is using double click for handling the next line processing and then the single click can be processed for the url, but if you have your own system now, that's also great!

[CharlieDelune]

@Iakobs That's a good solution too. For me, double-click vs single-click was a non-starter. I was pretty rigid that I wanted single clicks on specific words (which have a different colour) to do one thing, and then single-clicks anywhere else to do the other thing.