APub → Paragraph Panel → Decorations -[Dark theme] no gap between [Add] [Remove] decorations buttons. Glued together.

[bbrother]

Quote

UI has a key impact on user experience. It should be made with attention to the smallest details.

App: APub 2.5.2 (windows)

Theme: Dark

UI issue in Paragraph panel → Decorations:

• no gap between [Add][Remove] decorations buttons. Glued together

[PMan]

12 hours ago, bbrother said:

App: APub 2.5.2 (windows)

Theme: Dark

UI issue in Paragraph panel → Decorations:

• no gap between [Add][Remove] decorations buttons. Glued together

I have no problem as can be seen here 

 

I have found (in the past)  that re-installing may solve problems

 Asus Vivobook 15  Intel I7 processor,  Intel Iris X graphics, Windows 10 Home Version 20H2 (64 bit),  32GB RAM.  
Affinity Designer 1.10.5.1342, Photo 1.10.5.1342, Publisher 1.10.5.1342 
Affinity Designer Beta 1.10.5.1342, Photo Beta  1.10.5.1342, Publisher  Beta  1.10.5.1342
Affinity Designer2 V2.5.2, Photo2 V2.5.2,  Publisher2 V2.5.2
Affinity Designer2 V2.5.2.2486 (Beta), Photo V2.5.2.2486 (Beta), Publisher V2.5.2.2486 (Beta)

 

[bbrother]

The buttons should not be glued together. There should be a gap between them. It's a matter of good practice and consistency in user interface design.

In the light theme there is a gap between these buttons. It should be the same in the dark theme.

[Affinity Info Bot]

The issue " [Dark UI] no gap between [Add] [Remove] decorations buttons." (REF: AF-3446) has been fixed by the developers in internal build "2.6.0.2551".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

[Affinity Info Bot]

The issue " [Dark UI] no gap between [Add] [Remove] decorations buttons." (REF: AF-3446) has been fixed by the developers in the latest beta build (2.6.0.2805). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.