8000 SEGSAdmin in MacOS defaults to home directory and not ./data/ when started from Finder · Issue #960 · Segs/Segs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

SEGSAdmin in MacOS defaults to home directory and not ./data/ when started from Finder #960

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and 9015 contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Open
mobbyg opened this issue Aug 14, 2022 · 0 comments
Open

SEGSAdmin in MacOS defaults to home directory and not ./data/ when started from Finder #960

mobbyg opened this issue Aug 14, 2022 · 0 comments
Labels
bug Verified bug

Comments

@mobbyg
Copy link
Collaborator
mobbyg commented Aug 14, 2022

Describe the bug

When running SEGSAdmin from the Finder window, MacOS will default to the user's home directory and not the directory that the exe was started from. But if you run it from Terminal, it functions as expected.

To Reproduce

Steps to reproduce the behavior:

  1. In Finder window, navigate to your SEGS folder.
  2. Double click SEGSAdmin to start it.
  3. When going through the setup, configs, pigg files and dbs will not be copied or created to the folder the Admin is running from. output to the terminal shows it's a folder called data in the user's home directory.

Expected behavior

When double clicking the exe, it should open the SEGSAdmin and default to the directory it was opened from.

Screenshots or Attachments (if applicable)

pigg and binconverter processing screen in SEGSAdmin, when run from Finder:
Screen Shot 2022-08-13 at 12 06 42 AM

When run from the terminal
Screen Shot 2022-08-13 at 10 58 26 PM

SEGS Version, C++ Toolkit

  • SEGS Build ID:
  • C++ Toolkit:
@broxen broxen added the bug Verified bug label Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Verified bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mobbyg @broxen
0