To be consistent with any other widgets, GUI elements:

• the Menu._main should be rename to Menu.update
• the Menu.draw should take surface as argument
• the Menu.mainloop should take the surface, and bgfun arguments (remove them from Menu constructor)
• the _dopause attribute can be trashed

This is to ease the use of the menu, with less parameters in the Menu constructor. But only a proposition, of course ;-). It's imply lots of changes.

Thus 2 scenario for the end user:

1. Let's pygame-menu do the event loop:

def draw_background():
    ...

mymenu = Menu(...)

mymenu.mainloop(surface, bgfun=draw_background)

2. User's application manage the event loop:

def draw_background():
    ...

mymenu = Menu(...)

While True:
    draw_background()

    events = pygame.event.get()
    for event in events:
        if event.type == pygame.QUIT:
            exit()

    mymenu.update(events)

    mymenu.draw(surface)

    pygame.display.update()

As discussed in #162 this PR integrate themes for pygame. This makes a lot of changes, from the Menu constructor to widgets. Also examples were updated.

Added ".copy()" feature to Themes, because each theme object must be different for each menus.

Hi,

After some weeks, I finally found the time to make this PR.

Concerning your previous remarks about #8 :

1. The backspace button is now disabled

2. The "word ellipsis" on too long text input is not yet implemented, I will propose it in another PR (because not enough time for the moment)

3. Events from navigation are ignored on a text input

General remark about the rework that I have performed:

1. All elements of a menu are now a widget. This implies more custom classes and objects, but it gives the advantage of:

a. Avoid managing all events in the same function (each widget has its own update() method) b. Going in the way of #18 c. Widget position can be moved easily, it will be easier to implement #15 in the future

2. A new attribute _top has been added to keep reference to the top level menu. However, I think that the management of change between menu (open/close) is quite difficult to manage with the current code (for instance when we need to use the _actualattribute?). Maybe a handler class can be developed to manage the changes between menus.

Callback management

I have standardize the way to call the callback function. All widget that can receive/change their values (implements the get_value() method) automatically provide the current value to the onreturn and onchange callback as first argument. This change imply breaking the compatibility with previous version of pygame-menu. Managing callback in such a way, permits to keep constancy between function signature. I let you decide if this is acceptable for the version 2.0.

Fill free to update/change anything.

anxuae

A input text option to menu would be nice, but i don't know how to gather all keyboard events without "event crash" with the main menu, maybe using a inner mainloop to gather events should work.

When I am making a custom theme from an existing theme and use background.color with pygame_menu.baseimage.BaseImage to set a custom image as menu background the image appears fine but if I go into a submenu then back into the main menu the submenu bar does not disappear.

Environment information Describe your environment information, such as:

• SO: Windows 10
• python version: v3.10.1
• pygame version: v2.1.2
• pygame-menu version: 4.2

Describe the bug Hi,

I just started to design a game in python based on PyGame and Pygame-menu.

When I try to execute the simple.py example, I get this error that I can't explain to myself:

Hello from the pygame community. https://www.pygame.org/contribute.html
pygame-menu 4.2.0
Traceback (most recent call last):
  File "d:\User\Dougdoug\Projects\reallybasicpong\main.py", line 50, in <module>
    menu.mainloop(surface)
  File "D:\Software developmentPython\lib\site-packages\pygame_menu.py", line 2910, in mainloop
    self.update(pygame.event.get())
  File "D:\Development softwarePythonlibSite-packagespygame_menu.py", line 2439, in update
    selected_widget.update(events):
  File "D:\Development softwarePython\lib\site-packages\pygame_menu\widgets\widget\textinput.py", line 1570, in update
    self._check_mouseover(event, rect)
  File "D:\Software developmentPython\lib\site-packages\pygame_menu\widgets\core\widget.py", line 692, in _check_mouseover
    if event.gain == 1:
AttributeError: 'Event' object has no attribute 'gain'

On the other hand, I manage to execute correctly the other examples present on the repo without problems.

Any idea ?

Thanking you in advance.

Currently it's not possible (without a warning) to iterate through all widgets in a menu, because _widgets is a private attribute in the class Menu. Adding a property fixes this problem:

@property
def widgets(self):
return self._widgets

I guess this was done on purpose, but why? I'd like the option to access all widgets that my menu contains (e.g. to insert a widget at a specific place in the menu).

Now that we have the arrows working, another functionality I'd like to add is to make the arrows blink, if so desired by the user. Here's my end goal:

Is your feature request related to a problem? Please describe. I am trying to define a menu with a border, as in this example:

The borders are defined in this file:

Describe the solution you'd like I would want to be able to define a border for the menu, so that pygame-menu is able to tile it (as opposed to stretching it) and place the corners appropriately. Ideally this option could be made part of a theme.

Describe alternatives you've considered I tried defining that as a background image, but then I would need to define it with the right final dimensions or it would be stretched. I also tried using menu.get_scrollarea().get_decorator().add_callable, achieving the image above. The problem with this solution is that I cannot define that in a theme, forcing me to modify each menu separatedly or to create a subclass of Menu that applies this by default.

Any idea what would be required to make it possible to have two columns of items in a menu? I see that there's a "left" and "right" direction, so maybe this was an intended feature?

I'm glad to help implement it.

Environment information Describe your environment information, such as:

• SO: linux/Raspberry OS
• python version: v3.7
• pygame version: v2.0.1
• pygame-menu version: v4.0.7-master

Describe the bug Scroll bar doesn't respond to touch on the screen. I can't drag the slider from the scroll bar. At some point I try to touch lower in the scroll bar to see if at least I can go down not dragging but jumping to the lower section (I don't know if this make sense), but it also doesn't work. Same test in the computer with the mouse works perfectly. When I try to slide the scroll bar, it seems to gets selected because it changes color, but nothing happen.

To Reproduce I copied the scroll_menu example and added touchscreen=True in all menus. The result is I can select buttons, go inside other menu and go back with the X, but scroll bar doesn't respond to touchs.