Kurt,

What OS are you running on? On Linux, it may be possible to script a screen scrape. Also, one would think Copy / Paste would be easy, but from a programming perspective, it is actually more complicated than simply opening and writing to a file. I can check if the window control for the asm/linker output supports copy natively already and simply needs to be enabled (it's possible).

Screen dump is already available through the Telnet / Socket connection, or if you are running under Linux, you can simply type "screen_dump" or "sd" for short, and it will scrape the screen contents as text. The socket connection has to be enabled from the Tools->Socket Configuration menu.

Ken

On 3/17/16 11:05 AM, Kurt McCullum wrote:
Sure but that would only give me an image of the screen. I need the actual text to work with.

Kurt


On Thursday, March 17, 2016 10:52 AM, Mike Stein <[email protected]> wrote:


Can't you just PrtScr(een)?

    ----- Original Message -----
    *From:* Kurt McCullum <mailto:[email protected]>
    *To:* Model 100 Discussion <mailto:[email protected]>
    *Sent:* Thursday, March 17, 2016 1:32 PM
    *Subject:* Re: [M100] Virtual-T IDE Question

    Ken,

    Everything I need to copy is in the error window on the screen but
    I can't copy it to the clipboard. Would that be easier than
    writing to a file?

    Kurt


    On Thursday, March 17, 2016 10:12 AM, Ken Pettit
    <[email protected] <mailto:[email protected]>> wrote:


    No.  It would be super simple to add though ... the assembler and
    linker already output through a common "stdout" handler
    (VT_Ide::Stdout in the ide.cpp file).  Would be a simple matter
    adding a line of code to also print any messages to a file.  The
    most time consuming thing would be to add a GUI checkbox to enable
    it, and maybe an edit field / browse button for the filename, and
    even that isn't much.

    Ken

    On 3/17/16 9:53 AM, Kurt McCullum wrote:
    Is there a way to export the assembler error messages to a file?

    Kurt







Reply via email to