Maic Siemering

@dependabot recreate

@tmokmss That is a good question, did not think about that. I will check, otherwise we would have to introduce a property.

Update: Our PR was basically rejected, because the proposed solution does not cover all requirements. I changed the issue description accordingly.

Hi, I think I would need this flag, but maybe it is better to describe my use case, there might be another solution for it with uv: I want to...

Thank you for the feedback. I guess we can keep this issue open until we complete the current epic (browser support) and discuss the suggestion afterwards :)

1. that would be great :) 2. at least for GUI that is how the event handler look like, they only get the event (and self)

Initial setup is merged and released with 3.2. I will keep iterating on the support to ship it out of the experimental subpackage

Where to put it? ``` * GUI * Removed :py:class:`~arcade.gui.widgets.UIWrapper` this is now general available in :py:class:`~arcade.gui.widgets.UILayout` * Removed :py:class:`~arcade.gui.widgets.UIBorder` this is now general available in :py:class:`~arcade.gui.widgets.UIWidget` * Removed :py:class:`~arcade.gui.widgets.UIPadding`...

Ok, I will add my changes to it (in md format)

I fixed the example code to be runnable: ``` import arcade import arcade.gui print(arcade.get_display_size()[0], arcade.get_display_size()[1]) class StartingScreen(arcade.View): def __init__(self): super().__init__() self.ui_manager = arcade.gui.UIManager() self.ui_manager.enable() self.play_button_texture = arcade.load_texture( ":resources:onscreen_controls/shaded_light/start.png" ) self.play_button...