Skip to content


GUI stands for graphical user interface. It is a visual representation of communication presented to the user for easy interaction with the machine. It allows users to manipulate elements on the screen using a mouse, a stylus or even a finger. The actions in a GUI are usually performed through direct manipulation of the graphical elements.

Here are 10,628 public repositories matching this topic...

KOLANICH commented Jan 11, 2019

Sometimes it is needed to store compressed data in the DB. Unfortunately not all the DBs have built-in compression and FUSE compressed FSes are not available for every OS. So it may make sense to store compressed binary blobs in the DB.

Unfortunately when one sees them in DBeaver he sees them compressed, but often they are needed uncompressed. So it'd be nice to have a feature to decompress the

Madoshakalaka commented Nov 25, 2021

This is about:

  • Other (Important Tips)

Component communication might deserve a dedicated page.

Ancestor -> Descendant

straightforward: passing props. Using a context if the descendants can be too deep down the tree.

Descedant -> Ancestor

This is not very obvious. In fact, two people asked the same question on Discord in one day. And personally, I had no clue either despite h

AmanAgarwal041 commented Jun 23, 2022


Earlier the API auth error redirects the url of the application with query params response_status and display_message which used to show error toast in edit mode only. But now the logic has been moved to view mode and removed from edit mode for plugin datasource RestAPIDatasourceForm only.

Fixes #12600

Type of change

  • Bug fix (non-breaking change which fixes a
Bug Good First Issue Frontend High
haosdent commented Mar 22, 2022

Flameshot Version

Flameshot v11.0.0 (ad1bf28)
Compiled with Qt 5.15.2
darwin: 21.2.0
osx: 12.1

Installation Type

Using the ready-made package from Github Releases

Operating System type and version



When I try to add some text in the screenshot, suppose I am tying

"hello", then I type Esc key.

Then all my input would become lost. What my expectation

Enhancement Good first issue
sourcebox commented May 31, 2021

I'm working on an application which mainly consists for sliders for parameter control. For better user experience, it would be nice to offer two features: reset to default and fine control.

On VST plugins this is normally done via double-clicks and/or modifier keys. E.g. double-clicking resets the slider to a default (mostly 0), alternatively Ctrl-/Cmd-Klick also does it. For fine control, ofte

feature good first issue widget
ret2libc commented Jun 15, 2022

Environment information

  • Operating System: Fedora 36
  • Cutter version:
  • Obtained from:
    • Built from source
    • Downloaded release from Cutter website or GitHub: ./Cutter-git-2022-06-12-84b33d50bdd666825eada79a5fe0a2039bc2b1c6-x64.Linux.AppImage
    • Distribution repository
  • File format: any

Describe the bug

There is a black background which is quite bad to see

good first issue
klieret commented May 28, 2019

Type of Issues (Enhancement, Error, Bug, Question)


  1. Initialize Window
  2. Show it (window.Read())
  3. Run window.Disable()
  4. The whole desktop environment freezes, nothing is clickable anymore
  5. Change to tty terminal and kill application
  6. Things are normal again

Operating System

Ubuntu 16.04 LTS 64 bit

Python version

Python 3.5.2


enhancement good first issue documentation Performance Improvement
X-Ryl669 commented Feb 3, 2022

Describe the feature request

Since LVGL is more and more used as an desktop app too, I think it's necessary to have a clean application exit event too.
Right now, all example have a while(1) { } in their main function so when you close the app (by clicking the X icon, or Alt+F4 or ...), you're actually leaking all the application objects.

For most of them, it's not important, but som

emilk commented Feb 20, 2021

Tracking issue for improving the egui docs. Other suggestions for improvements welcome!

All doc-examples need to be part of the doctests (i.e. they should never be marked ignore, though no_run can maybe sometimes be motivated).


The crate-level docs for egui (at generated from egui/src/ sh

help wanted good first issue docs and examples

Related Topics