Skip to content
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

Usability Issue #52

Closed
ghost opened this issue May 27, 2015 · 1 comment
Closed

Usability Issue #52

ghost opened this issue May 27, 2015 · 1 comment

Comments

@ghost
Copy link

ghost commented May 27, 2015

I was experimenting with the core mupen64plus and then I discovered this ui! It was working great for me. I experimented with a few different versions. I moved the app around to different folders and fairly quickly the links to the various dylibs were wiped. I was able to input them all correctly (I think), except I chose the wrong file for the first library. Now every time I launch the app, it just closes immediately. I was just curious where I could go to edit the file that I mislinked? Without being able to change it or remove it from my system, I have no idea how to use the app anymore (other than a complete system reinstall).

I'm on OS X. I imagine there's just a config somewhere that is linking that file. I checked the ~/.config folder and I saw it linking to everything except for the first one that is called library I think. Anyway, I even tried deleting the mupen64 folder inside of .config and it was to no avail. When it was recreated, the linking issue stood so I couldn't launch the app.

I think this would be helpful for others if they should make the mistake of linking the wrong file like I did (which I'm not 100% sure what the right one is but if I could edit it then I could at least do some trial and error).

@ghost
Copy link
Author

ghost commented May 29, 2015

This doesn't solve the issue that I described, but by renaming the file I was able to use the application again. I'm still curious if I can get this answered. At least I can use it again though.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants