tauri-apps / tauri-apps/plugins-workspace
[feat] Add option to disable CREATE_NO_WINDOW flag
- Dominant language
- Rust
- Stars
- 1.8k
- Forks
- 602
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 9
Description
### Describe the problem
```
export async function openREPL() {
const appDirPath = await appDir();
const command = Command.sidecar("bin/goalc", [
"--startup-cmd",
"(mi)",
"--proj-path",
`${appDirPath}data`,
]);
command.spawn();
}
```
The sidecar app that I'm spawning here, `bin/goalc`, is a console app. When I call this function I can tell that the application is running properly from Task Manager, however the console window does not open on the screen.
### Describe the solution you'd like
I'm not sure what the solution to this is.
### Alternatives considered
```
Command::new("start")
.args(&[*my external bin*, "--option", "args"])
.spawn()
.unwrap();
```
I considered writing functions on the rust side to launch my sidecar app, something along the lines of the code block above. However, I wasn't sure if I would be able to access the external binaries from rust easily. Also, I wanted to avoid multiple implementations for different OS.
### Additional context
_No response_
Contributor guide
Research direction
Start from the sidecar command path used by openREPL and the Rust process-launching code represented by Command::new. Check where the Windows CREATE_NO_WINDOW flag is applied and how sidecar options are exposed across operating systems. Done means callers can disable that flag for console sidecars without requiring separate platform-specific implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, tauri
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100