pipedconsole 0.0.2

Piped console is a (currently windows-only) rust crate wich allows you to easily manage two or more different consoles from within one process.
docs.rs failed to build pipedconsole-0.0.2
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: pipedconsole-0.1.2

Pipedconsole

Currently docs.rs isn't working correctly!!! This has to do with the building, the build will fail if you build for the first time! The problem is that docs.rs complains about this. (In general it's not easy to ship a binary with your crate, wich is build for every user individually.) ** I am very sorry for that and I am going to fix it ASAP, so there can be proper documentation!! **

A rust crate for managing multiple consoles from one windows application.

Normaly a program running on windows can only use one console.

A process can be associated with only one console, so the AllocConsole function fails if the calling process already has a console.

From the microsoft docs.

This crate solves this problem by providing an abstraction over a worker process wich is controlled using named pipes.

Usage

You can use the Console class to create a new console, after that you can write to it or read a line.

use pipedconsole::Console;

let console = Console::new("My Console").expect("Failed to create a new console");
console.println("What is your name?").expect("Failed to call println"); // a seperate console window

let mut name = String::new();
console.read_line(&mut name).expect("Failed to read from the console");
println!("Your name is: {}", name); // main processe's console

Documentation and download

Download the crate either directly through Cargo or visit crates.io.

More documentation can be found on docs.rs.