[GH-ISSUE #103] [Small Issue] Current-Command command specifications don't match text in ui #99

New issue

Closed

opened 2026-02-26 12:20:29 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 12:20:29 +03:00

Owner

Originally created by @Savvasun on GitHub (Jun 8, 2020).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/103

The command specifications in the Current Command textarea should match the descriptions that are written in "( )"s above the buttons in the UI:

What it says	What the UI shows
`--noconsole`	`--windowed`
`--nowindowed`	`--console`

The file that needs to be fixed is configurations.js
- A possible fix for this could be getting command data from the the index.html file

This issue is informative as well as a request. I may be able to fix this myself soon.

Originally created by @Savvasun on GitHub (Jun 8, 2020). Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/103 The command specifications in the Current Command textarea should match the descriptions that are written in "( )"s above the buttons in the UI: | What it says | What the UI shows | |----------------|-------------------| | `--noconsole` | `--windowed` | | `--nowindowed` | `--console` | * [ ] The file that needs to be fixed is `configurations.js` * A possible fix for this could be getting command data from the the `index.html` file ***This issue is informative as well as a request. I may be able to fix this myself soon.***

kerem closed this issue

2026-02-26 12:20:29 +03:00

kerem commented

2026-02-26 12:20:29 +03:00

Author

Owner

@brentvollebregt commented on GitHub (Jun 9, 2020):

Yep, this is incorrect, when you click the "Console Based" it should show --console and when clicking "Window Based" it should show --windowed.

Looking at options.map(x => x.option_strings) in the UI, it seems this option has three possible strings per state (console / window). A solution to this would be to always try to get the second string but use the first if there is no second; looks like this handles each option well still - verification: options.map(x => x.option_strings[x.option_strings.length === 1 ? 0 : 1]).

I've just put a commit into develop now, thanks heaps for this.

@brentvollebregt commented on GitHub (Jun 9, 2020): Yep, this is incorrect, when you click the "Console Based" it should show `--console` and when clicking "Window Based" it should show `--windowed`. Looking at `options.map(x => x.option_strings)` in the UI, it seems this option has three possible strings per state (console / window). A solution to this would be to always try to get the second string but use the first if there is no second; looks like this handles each option well still - verification: `options.map(x => x.option_strings[x.option_strings.length === 1 ? 0 : 1])`. I've just put a commit into develop now, thanks heaps for this.