Author Topic: RTB Dedicated Hosting Service  (Read 99663 times)

Then you're doing a horrible job wrapping a program.
Who needs to see that?

Who needs to see that?
Nobody. That's not the point. The point is you usually don't want to break functionality of the program so rerouting anything would be a bad choice. The better choice would be to listen for the software interrupt.
« Last Edit: November 16, 2012, 08:42:55 PM by Trinick »

Nobody. That's not the point. The point is you usually don't want to break functionality of the program so rerouting anything would be a bad choice. The better choice would be to listen for the hardware interrupt.
Why would you complicate it?

I wouldn't call that a complication, I'd call it doing it the right way. It's not complicated at all, just wait for the interrupt then grab the string off the stack.

Nobody. That's not the point. The point is you usually don't want to break functionality of the program so rerouting anything would be a bad choice. The better choice would be to listen for the hardware interrupt.
If Torque's console itself wasn't so ungodly loving horrid it wouldn't break anything.

Fun fact: That windows console window you see with Blockland is not actually a console or terminal. It's part of Torque. It doesn't listen to stdin - it captures keystrokes instead, and does all the printing itself. It still appears even if its output is rerouted somewhere else, unlike basically any other program.

Nothing is broken by wrapping the stdout from the console, at least no more so than it already was.

Nothing is broken by wrapping the stdout from the console, at least no more so than it already was.
Console no longer displaying text = broken functionality, regardless of how needed it is. I can guarantee doing it the low level way is faster, too.

Think we should bring this discussion back to how amazing I am.

Think we should bring this discussion back to how amazing I am.

Ok. You are amazing

Console no longer displaying text = broken functionality, regardless of how needed it is. I can guarantee doing it the low level way is faster, too.
If it was made properly that window would not be displayed at all when stdout is being captured already. You can display output in your capturing program. The functionality is broken because of its own poor design, and is reimplemented anyway.




Cheeky!

Is there going to be an app for Android too?

chrome and starbucks!
yah!

Is there going to be an app for Android too?

The application is actually web based so it should work on any decent phone. We decided to go for a web app as we can reuse the majority of the desktop's site code with a simple reskin on top which makes development quick and easy.

Just tested on Android, works fine.
« Last Edit: November 17, 2012, 06:24:58 AM by Rub »


Just shut up already. Stop acting like you are so superior to everyone else.

He does not act.