Closed Semnodime closed 2 years ago
This is on purpose because without the file extension URH has no chance to know about the format when you load it again. Therefore, without an extension the default .complex
format is assumed. More info can be found here.
I assume it would be wise, to (forcibly) add the extension according to the format selected in the "save as"-dialog instead of saving in a format that has not been specified.
My rationale is, that the format select won't even display which extension one currently must manually add, to make sure that the correct / selected format is actually used.
Isn't that done by the file manager anyway? At least on my system (KDE) it works like this:
It is not done on my system. That's why I noted, which Qt version I am using in the initial post.
That looks rather like a GTK file dialog. Do you see this desired behavior in other Qt programs?
Closing due to inactivity.
Expected Behavior
Save signal in selected format.
Actual Behavior
Saves signal in format determined by file extension irrespective of selected format during "save as"-dialog. Saving the signal as complex32unsigned ("file_a") and as complex16unsigned ("file_b") will result in the same hash sum.
Steps To Reproduce
Platform Specifications