Load entire appinfo.vdf since loading selectively is broken#55
Load entire appinfo.vdf since loading selectively is broken#55Jonathing wants to merge 1 commit intotralph3:masterfrom
Conversation
|
Sorry, could you show me the error? I can't reproduce. Are you by any chance using the Flatpak version? |
|
Here you go I am not using the Flatpak version. I am using the repo itself and have #!/bin/bash
/usr/bin/env python3 $HOME/Development/git/.quick-forks/Steam-Metadata-Editor/src/main.py $@Here are my config files: https://gist.github.com/Jonathing/111feccb983dfcb4133c340e99363cf6 |
|
I see. Can you send me your I don't think loading the entire file is a proper solution (at least not without a deeper investigation into the issue). |
|
Sure. Here you go: appinfo.vdf.zip I had to compress it into a ZIP file because GitHub wouldn't accept it otherwise. If you want me to upload it some other way, let me know. |
|
Updated the PR description with additional clarifications, since looking back on it it was probably a little rude (sorry 😅). My impression is that the python code-base is being put into a freeze while the GTK rewrite in #50 is being worked on, which is why I made this quick-fix PR. |
|
Don't worry, you didn't come off as rude. Yes, I don't want to touch the current codebase much, since it's done much better in the GTK version. I haven't had the time to take a look at the issue yet. If it ends up being too complicated I may end up accepting the PR. Cheers! |
Name entails. Normally this doesn't affect the user at all, but when trying to run the program with the
--silentflag, it immediately crashes due to an indexing error. It probably has something to do with how you are reading the VDF file. The reason I made this PR rather than simply opening up an issue was because since #50 exists, I'd imagine all the work into cleaning up how the application works would be put into the GTK rewrite.Of course, this PR is a really quick and dirty fix to a problem that I hope would be solved by the GTK rewrite. When this program is loaded in GUI mode, the "save" button indiscriminately writes to the entire
appinfo.vdffile, since it doesn't load it selectively like the silent or export flags do. Since this merely makes it so that silent mode loads the entireappinfo.vdffile, just like how it would in the normal GUI mode, the only real impact here is performance.