Avian Waves
®
\
Forums
\
RD Tabs
\
RD Tabs Suggestions
\
Better scripting support
Register
Login
Search
Blog
About
Software
Tools
RD Tabs
Legacy
XS BAP
VSCMap
SCHANNEL ADM Template
XS EDB Limit Changer
RemovableStorageDevice ADM Template
Windows Mobile Classic
Music
Discography
Avian Waves
TCX - All We Can Do
Studio
The Black Room
Keyboards
Rack Synths
Effects Processors
Mixing
Monitoring
Interfaces
Sequencing & Editing
Instruments Plugins
Effects Plugins
Contact
Forums
Blog
About
Software
Tools
RD Tabs
Legacy
XS BAP
VSCMap
SCHANNEL ADM Template
XS EDB Limit Changer
RemovableStorageDevice ADM Template
Windows Mobile Classic
Music
Discography
Avian Waves
TCX - All We Can Do
Studio
The Black Room
Keyboards
Rack Synths
Effects Processors
Mixing
Monitoring
Interfaces
Sequencing & Editing
Instruments Plugins
Effects Plugins
Contact
Forums
Welcome Guest! To enable all features please try to register or login.
×
Avian Waves Forums
Search
Help
×
Avian Waves Forums
RD Tabs
RD Tabs Suggestions
Better scripting support
Better scripting support
Previous Topic
Next Topic
Tools
Watch this topic
Print this topic
Atom Feed
RSS Feed
clayg
52.4% (Neutral)
Nestling
Topic Starter
2008-09-05T00:13:32Z
#1
Specify "console" session from command line
Ability to suppress the 'writes to the console asynchronously from a separate thread" - I want it to just do my bidding, go away and return control immediately
Also, maybe someone could just explain how I'm supposed to be doing this part...
Silly Basic Example:
create a basic .bat file:
"c:\program files\avian waves\rd tabs\rdtabs.exe" start server [ipaddr] /u:[user] /p:[pass] etc.
rdtabs starts up and opens my connection - perfect.
You can keep running your little batch file and starting new sessions all day, but once you CLOSE that command prompt - it won't start any more sessions in this manner. You have to exit rdtabs and start a new instance.
I don't know maybe it's just me... maybe it's a bug. Any insight would be appreciated.
Edited by user
2008-09-05T15:51:52Z
|
Reason: Not specified
View All Posts by User
Timothy
100% (Exalted)
Flock Leader
2008-09-06T12:03:57Z
#2
Good idea on specifying console and also the warning supression. That should be easy -- I can add those settings to the Options.
As for the second problem, RD Tabs may lose the ability to write messages to the console if invoked from a different console than the one it was alunched, but it SHOULD still respond to the commands. (This is why there is a "View Console Window Output" in the help.)
Hmmm... I just did some testing. If I start RD Tabs from the start menu, I can start new connections from a different command prompt. But if I start it from a command prompt and invoke another command prompt and view the console output (under help), I see an exception. Can you confirm you are getting this exception too? I should be able to figure this out as it is pretty clear where the problem is occuring, I just want to see if you can confirm having the same bug.
Also, are you running RD Tabs 32-bit or 64-bit? I just tested on 64-bit. Thanks.
*** Exception ***
System.IO.IOException: The handle is invalid.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.__ConsoleStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.TextWriter.SyncTextWriter.WriteLine()
at RDTabs.CommandLine.ProcessCommandLine()
View All Posts by User
clayg
52.4% (Neutral)
Nestling
Topic Starter
2008-09-06T15:42:09Z
#3
Thanks for feedback, I appreciate your positive response.
I'm running 32-bit
Let me see if I can confirm that exception for you.
*** Exception ***
System.IO.IOException: The handle is invalid.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.__ConsoleStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.Write(Char[] buffer)
at System.IO.TextWriter.WriteLine()
at System.IO.TextWriter.SyncTextWriter.WriteLine()
at RDTabs.CommandLine.ProcessCommandLine()
I confirm that the exception will not occur is I start the instance w/o command line optoins. ie from the start menu - or even just first launching 'rdtabs.exe' from the command prompt and then closing that shell.
Edited by user
2008-09-06T15:53:01Z
|
Reason: Not specified
View All Posts by User
Timothy
100% (Exalted)
Flock Leader
2008-09-08T15:29:53Z
#4
I fixed the bug for version 2.1.18. The fixed version should be out soon (give me a couple days to fix a few more things). The WinForms Warning will be an option in 2.2, so you'll just have to suffer through that for now. 🙂
View All Posts by User
clayg
52.4% (Neutral)
Nestling
Topic Starter
2008-09-10T21:08:47Z
#5
Wow. That's amazing. Thank you. I'll look forward to the update!
View All Posts by User
clayg
52.4% (Neutral)
Nestling
Topic Starter
2008-09-19T16:11:22Z
#6
I verified the Exception has been corrected in Version 2.1.18
Thank you so much for that!
I'll look forward to the WinForms Warning Suppression and console login options in future version, keep up the work on this great tool!
View All Posts by User
Atom Feed
Rss Feed
Similar Topics
SOCKS/HTTP proxy support
(
RD Tabs Suggestions
) by
Marilami
2022-06-29T08:43:31Z
Keratin Support for RD Tabs
(
RD Tabs General Discussion
) by
Timothy
2008-09-25T13:36:21Z
RD Tabs support
(
RD Tabs Support
) by
Timothy
2013-07-06T18:04:12Z
Dual Monitor Support
(
RD Tabs Support
) by
Skipmeister
2010-09-25T19:49:25Z
support for <CTRL> <ALT> <BREAK>
(
RD Tabs Suggestions
) by
Timothy
2008-12-01T03:28:53Z
Users browsing this topic
Guest
Avian Waves Forums
RD Tabs
RD Tabs Suggestions
Better scripting support
full film