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

KIS.cfg slot size set to 100, please set to 50. #58

Closed
zer0Kerbal opened this issue Jan 21, 2022 · 0 comments · Fixed by #106
Closed

KIS.cfg slot size set to 100, please set to 50. #58

zer0Kerbal opened this issue Jan 21, 2022 · 0 comments · Fixed by #106
Assignees
Labels
issue: config issue type state: approved Approved to proceed. type: request Requested functionality, features, pages, workflows, endpoints, etc. work: obvious The situation is obvious, best practices used.

Comments

@zer0Kerbal
Copy link
Owner

From CoyoteCargoFreighter created by zer0Kerbal: #33

From CSI-Cargo-Freighter created by BararQ: dboi88#59

KIS.cfg
The slot size was set to 100, which when it opens, it covers my entire screen and cuts out some parts. I set it to 50.

@zer0Kerbal zer0Kerbal added issue: config issue type state: approved Approved to proceed. type: request Requested functionality, features, pages, workflows, endpoints, etc. work: obvious The situation is obvious, best practices used. labels Jan 21, 2022
@zer0Kerbal zer0Kerbal self-assigned this Jan 21, 2022
@zer0Kerbal zer0Kerbal changed the title KIS.cfg slot size set to 100, needs to be 50. KISBAY.cfg slot size set to 100, please set to 50. Jan 21, 2022
@zer0Kerbal zer0Kerbal added this to the Release 0.4.0.0-Adoption milestone Jan 21, 2022
@zer0Kerbal zer0Kerbal changed the title KISBAY.cfg slot size set to 100, please set to 50. KIS.cfg slot size set to 100, please set to 50. Jan 21, 2022
@settings settings bot removed this from the Release 0.4.0.0-Adoption milestone Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: config issue type state: approved Approved to proceed. type: request Requested functionality, features, pages, workflows, endpoints, etc. work: obvious The situation is obvious, best practices used.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant