ditto

I have an application that ditto won’t show results
if it ditto is run after the application starts.
Anyone have an idea what I might be stepping
on that keeps ditto from working?

Thanks,
Carlos

Carlos Clarke <carlos@ptdprolog.net> wrote:

I have an application that ditto won’t show results
if it ditto is run after the application starts.
Anyone have an idea what I might be stepping
on that keeps ditto from working?

How big is the screen that you are running ditto from ?
I’ve had problems with big pterms not working with ditto…

Cheers,
-RK


[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/

On 15 Sep 2003 12:35:29 GMT, rk@parse.com (Robert Krten) wrote:

Carlos Clarke <> carlos@ptdprolog.net> > wrote:
I have an application that ditto won’t show results
if it ditto is run after the application starts.
Anyone have an idea what I might be stepping
on that keeps ditto from working?

How big is the screen that you are running ditto from ?
I’ve had problems with big pterms not working with ditto…
I’m not running Photon.

I’m running 10 consoles at 80 columns x 50 lines.

Cheers,
-RK

Carlos Clarke <carlos@ptdprolog.net> wrote:
CC > On 15 Sep 2003 12:35:29 GMT, rk@parse.com (Robert Krten) wrote:

Carlos Clarke <> carlos@ptdprolog.net> > wrote:
I have an application that ditto won’t show results
if it ditto is run after the application starts.
Anyone have an idea what I might be stepping
on that keeps ditto from working?

How big is the screen that you are running ditto from ?
I’ve had problems with big pterms not working with ditto…
CC > I’m not running Photon.

CC > I’m running 10 consoles at 80 columns x 50 lines.

Two thoughts.

Is your screen updating frequently enough at a high enough priority
that ditto can’t get in?

Can you use the “prtsc” utility to capture the source screens image?
I meant this to test the underlying console_read() call.
But I guess you may be able to look at prtsc as a very week substitute
too.

OK. Here’s a third. You might be interested in looking at the
console_read() and other console_*() functions and write your own
ditto.


Bill Caroselli – Q-TPS Consulting
1-(708) 308-4956 <== Note: New Number
qtps@earthlink.net

On 17 Sep 2003 13:14:17 GMT, Bill Caroselli <qtps@earthlink.net>
wrote:

Carlos Clarke <> carlos@ptdprolog.net> > wrote:
CC > On 15 Sep 2003 12:35:29 GMT, > rk@parse.com > (Robert Krten) wrote:

Carlos Clarke <> carlos@ptdprolog.net> > wrote:
I have an application that ditto won’t show results
if it ditto is run after the application starts.
Anyone have an idea what I might be stepping
on that keeps ditto from working?

How big is the screen that you are running ditto from ?
I’ve had problems with big pterms not working with ditto…
CC > I’m not running Photon.
CC > I’m running 10 consoles at 80 columns x 50 lines.

Two thoughts.

Is your screen updating frequently enough at a high enough priority
that ditto can’t get in?

Screen updates aren’t very often.

What is interesting is that if I start ditto before the application it
works but not if I start it after the application.

Can you use the “prtsc” utility to capture the source screens image?
I meant this to test the underlying console_read() call.
But I guess you may be able to look at prtsc as a very week substitute
too.

OK. Here’s a third. You might be interested in looking at the
console_read() and other console_*() functions and write your own
ditto.

I was considering that but I thought that ditto used those functions
and I didn’t want to build something just to find out I was hitting
the same brick wall.

What I’m really looking for is someone at QNX to tell me how ditto
works to see if I’m stepping on something that it uses.