-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Save dialogue - Glitchy filename test #5193
Comments
Meanwhile, the original issue I tried to solve has seem to have been at least partially fixed... 🐳 I'm looking into the possibility of reverting, in order: #2230 has changes in it that should be kept but it may be least messy to revert it in it's entirety and pull those again separately. I will try and update my machine and test the issue first to see the state of it before proceeding. In order to test the issue on lmms 1.1.3 or older. Create an issue "test.mmp" The case above is if you go along with the project name as your render name. If you instead type in a new name altogether for the rendered project the issue seem to be there still. |
@zonkmachine When do you have time to solve this? |
"May be messy" sounds like "should be master". Perhaps a better question is... is this needed for 1.2? |
Two weeks, no answer. Re-milestoning. |
May I take this one ? |
Yes indeed but I would caution against it. I think your looking at a rewrite rather than troubleshooting. I was the one to mess this up and I failed to fix it in stable-1.2. After many changes in master it's beyond what I can handle but I'll be happy to test a PR. |
So assign it to me and I'll have a try. |
I took some time reading the different issues and comments related to this issue and this is one idea to implement. [Updated] This would force the creation of file with valid suffix. |
As the usage of mmpz or mmp is based on configuration, we could have the filedialog only proposing the possible format and then the file dialog would have always only one possible format on a selected format line. |
OK. That at least sounds familiar. I'll look into this after the weekend and try and replicate the issue/s.
But that is only the default file format. You can always change format later on actually saving. |
New Strategy : Seems to simple but logical for me. |
Yes it would be good to have a test case cause I was not able to reproduce for the moment on Linux Ubuntu. I think the Save has no issue and the export should be addressed with #5744. |
@MrTopom We want to close 1.3 and thus, we could need a fix for this issue soon. Do you want to write a PR (in this case we could support you), or should someone else do it? |
@JohannesLorenz i believe the OP is inactive. |
How about showing the save dialog after, rather than before, the export dialog? The reason we sometimes have to change the extension is that we show the save dialog before we know what the extension should be. |
Last time I looked into this issue I couldn't recreate it. I'm pretty sure the issue is still there, it's just a bit tricky to call forth. I'm removing this from 1.3 for now. I'll try to provide a demo project. |
As mentioned here, there is a remaining problem with the save dialogue.
Quote by @tresf
Basically, we test for already existing files to avoid saving over them. We also test for existing file minus suffix as you can enter just the name and let LMMS/Qt add the suffix but this earlier didn't test for the proposed name 'with' suffix so, as an example, saving the project 'test' when 'test.mmp' was present would save over test.mmp (See #2230).
The remaining issue is that all occasions of the suffix is removed from the filename when testing. Not only the suffix proper on the end.
Related pull requests: #2230 #3526 #4768
The text was updated successfully, but these errors were encountered: