Could you explain what problem you are solving with this?

In the export dialog we have static components and dynamically loaded. At the time export dialog is positioned on the screen we only know about static ones -> and it is positioned correctly in the center. But when dynamic components are loaded, the dialog grows in height but the dialog does not reposition itself again: that means a part of the dialog gets rendered below the screen and it's not visible.

This is just a hack to move window a bit more to the top so it doesn't matter which format you choose, you always see entire dialog on the screen.

Do you have any ideas how to solve that riddle without this ugly hack?

These refer to the UI framework from within an application-logic source file. We had this discussion about the delete behavior (https://mu--se.slack.com/archives/C06RX437GJV/p1755682183400249 - restricted access) and there's a way of keeping this ui-agnostic here and converting to a ui-specific type in a view directory.
This is a bit more work, though, so I'm not sure it's worthwhile. Only if you have some spare energy and you don't find the idea too silly :)

If possible I'd really like to reduce all possible fat off of this big, big source file. Things I see possible:

• Gathering those properties that are used in 6 different place in a dedicated file, as explained in an inline comment.
• Place the components defined at the bottom of the file in their own source files.
• Use the RadioButtonGroup with id: channelsGroup properly, making use of its model property (see DeleteBehaviorPanel.qml for an example)
• Use Row and Column in place of RowLayout and ColumnLayout where possible ?

1. All of these components are so small after a cleanup that it doesn't really make sense to me to put a separate file with this for example:

Component {
        id: enumComp
        StyledDropdown {
            property var option

            model: option.names
            currentIndex: option.value

            onActivated: function(index, value) {
                dynamicOptionsModel.setData(dynamicOptionsModel.index(option.index, 0),
                                            option.values[index],
                                            ExportOptionType.ValueRole)
            }
        }
    }

left it as is

2. About RadioButtonGroup: I have it planned to do here: Implement custom mapping for export channels #8963