Created attachment 166145 [details]
Top: first step, bottom: second step, when trying to run an executable

SUMMARY
Can you combine the two steps required for running an executable into one and solve the inconsistencies and other things?


STEPS TO REPRODUCE
1. Download CPU-X.AppImage (like from here: https://github.com/TheTumultuousUnicornOfDarkness/CPU-X/releases/tag/continuous) or use another non-previously used executable
2. Double-click on it or with it selected, press Enter

OBSERVED RESULT
1.
First there's a pop-up window named "Dolphin" asking:
"What do you wish to do with this file?" and two buttons (Execute and Cancel)
If Cancel is pressed it goes away of course.
If Execute is pressed, another pop-up window appears name "Warning - Dolphin" not asking anything, but informing:
"This will start the program X"
"If you do not trust this program click Cancel" and two buttons (Continue and Cancel)
2.
The first checkbox also has a "Do not ask again" checkbox, which is not ticked by default and it's obeyed.
The second doesn't have such checkbox, but a "Do not ask again" behavior seems to be enforced by default and there's no way to change that, like for security purposes where you would want to be asked every time.
3.
 CPU-X takes a while to load and show up making you think that it maybe did not register the clicks or Enter as there's no indication of waiting to appear. If you try more to open it, it will open multiple times.
4. 
The "Execute" and "Continue" buttons are not highlighted / selected by default, but "Cancel is, on both pop-ups



EXPECTED RESULT
1.
If the program, script, whatever, is new, show only one step, one pop-up window, with everything, warnings and questions, like:
"Do you want to make this program / script executable and run it?" with "Yes / No" buttons or "Yes / Cancel" buttons, even though I find the Cancel a bit weird.
2.
Have a "Don't ask again" checkbox too, which should work for both actions, not ticked by default and obey that behavior
Unless you put another button like "Yes and don't ask again".
Honestly I think it would be better to have to types of Yes buttons, one for one time and the other with the never ask again behavior than having to tick a checkbox and then press the Yes button.
It seems faster and easier for me, even though visually might be a bit strange.
But since there's enough space in the pop-up to put another button, I would be ok with that.
3.
Show a loading animation until CPU-X, or whatever AppImage / script we try to run, starts
4. 
Please highlight / select the "Yes / Continue" button by default so we can just press enter!
This baby-proofing is annoying and time wasting.
I think there was a similar discussion about this for the pop-up that appears when when SHIFT+DEL and most of the people wanted the "Yes / Continue" button to be selected.
I understand that the purpose here is a bit different as it's for security, but this is not impeding anyone to do a insecure action, it will just delay it, annoying the person in the meantime.
And also annoying the others who know what they are doing.

In my opinion, you should put a preference option somewhere in the settings where the user can specify if it's a beginner or advanced user so these pop-up buttons have the baby-proof option selected by default or the one most likely that the user wants, like permanently deleting the file or running the executable.
Otherwise there will always be a stress between the developers wanting to baby-proof dangerous or potentially insecure actions for new users and advanced users that are just annoyed for having their time wasted, a bit at a time.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Graphics Platform: Wayland
Installed ISO: neon-testing-20240207-1524.iso
Fully up to date: 2024-02-27