buttonic | A rich CSS button library built with LESS | Theme library

You could increase the radius of your BorderRadius to match the radius of the buttonIcon and give buttonIcon some padding.

Something like this:

If you want to draw on an image that will be displayed in a QLabel then it is better to load the image with opencv, draw the circle, convert the numpy array to QImage, convert the QImage to QPixmap and set it in the QLabel:

To combine a Icon on a Swing JButton seamless with a JavaFX Text I did the following:

1. Load both Icon and RolloverIcon onto the JButton so that the Image is already loaded
2. because awt Images are asynchronous and need to be loaded to be altered
3. Create a FXButtonFont(extends FXJPanel) object within the ButtonIconHover(extends JButton) constructor
4. all following calls are made within a nested Platform.runLater because we will need the JavaFX Thread
5. call on the JFXPanel getScene and on the Scene snapshot(WritableImage)
6. use SwingFXUtils.fromFXImage(WritableImage, null) to convert the WritableImage to BufferedImage
7. then call a self written mergeImages wich combines two BufferedImages into one
8. now set the returned BufferedImage as setIcon to the JButton

Here the modified ButtonIconHover:

The triggering of the tooltip for hovering is based on the mouseOver and mouseLeave events. mouseOver events get triggered for disabled buttons, but mouseLeave events do not. When you hover over a disabled button it triggers opening the tooltip, but when you leave the disabled button the mouseLeave event is not triggered so the tooltip stays open.

You have code (title={disabled ? "" : tooltip}) that suppresses the tooltip text when it is disabled, but the tooltip still thinks it is "open". Then when you enable the button, the text of the tooltip is restored and immediately displays. So which buttons this occurs on depends on which disabled buttons you happened to hover over while they were disabled.

You can fix this by explicitly controlling the open state of the Tooltip using the open, onOpen, and onClose properties. onOpen fires when Tooltip thinks it should open and onClose fires when Tooltip thinks it should close, but you can combine this information with additional information (e.g. the disabled state) to decide on the value of the open property.

Below is a working version of ActionButton. The useEffect call is to handle the case where the tooltip is open as you click on the button. If the button is disabled by the click, then onClose won't fire when leaving the button since the mouseLeave event won't be triggered for the disabled button, so the effect handles closing the tooltip in that case.

QStackedLayout works with "pages" which are reusable, just like a "tabbed" interface does (in fact, QTabWidget uses a private QStackedWidget, which is based on QStackedLayout).

Considering the fact that pages are reusable, your issue is that you're not actually switching to the pages, but you're continuously adding a new page every time.

While dynamic creation of pages is obviously possible, even for optimization purposes, in your case you don't need that since you only have 3 pages.

Since those 3 pages will probably have their own "static" layout, a better solution is to create separate subclasses for each page, which allows creating specific function to update the data whenever required. This is a far better approach than creating single functions that do almost the same thing when creating/switching pages, and you can have a single interface to access/set the data from and to each page.

This is a possible implementation:

In your way, you are directly calling the login function when component is rendering.

You just need to modify your use of component like this

Try something like this:

Ok so for starters, lets address this:

You can try: