roundbutton | 可设置圆角背景边框的的按钮

Alignment only works when the Layout size is bigger than the item size. So for example if layout's height is 200 and item's height is 100, then when you align vertically, the item will have 50 pixels on either side. But if the item is also 200 pixels, then it just fills it. In your case the PlayerSelector has the same height as the RowLayout, and is therefore aligned. The other items are not aligned in this case.

IMO there are two approaches in sizing a layout and its children:

1- Explicit sizes go from parents to children: you explicitly specify the size for the layout, and the size of children is relative to the size of layout. This is my personal preference since it is easier to make sure everything is sized and aligned correctly. When screen is resized things just shrink or stretch proportionately. In this approach only use Layout attached properties for both size and alignment.

2- Size of layout is implicitly defined from the size of the child items. (your approach) This approach can be more flexible and give you non-stretched but functional layouts when screen size changes, but there are more degrees of freedom for things to go wrong when screen is resized. In this approach, you can use (preferably) implicit or explicit sizes for children, but alignment still should be handled by Layout attached properties.

In your case it seems that the layout's height is set to the height of PlayerSelector (the largest height), so the other items are at the top of their row placement, and PlayerSelector is actually the only item that is vertically centered (it fills the whole height). So you could set alignment for all other items as well to make sure everything is centered.

The problem is that your asset is specific to a certain configuration, so if the configuration doesn't match with device settings then the drawable can't be found by resource and will lead to a crash.

Some variants are:

That should work with the Window from Qt Quick. Please create a bug report for that. Using ApplicationWindow does work though.

In the first case, you're saying what the function returns, but in the second case you're saying what the function is.

The second one is correct. React.FC is a function type. Your second block says your function is a React.FC, which means it accepts props: PropsWithChildren

, context?: any and returns ReactElement | null.

If you wanted to use function syntax rather than arrow syntax, you could write it as:

Try it:

You are creating a new Button in the constructor of class RoundBTN. This does not change RoundBTN at all.

The first thing you need to do in the constructor of class RoundBTN is to call the superclass constructor. Then you do not create a new Button but rather just set the style.

Your Glav class has a changed() signal but it doesn't do anything because your list property is constant (Q_PROPERTY( QLinkedList list READ list CONSTANT ))

You should change it to this:

This is my code for the rounded button with the green color you can modify it as per your convenience. Hope this will work.

button_rounded.xml