Conference bulova::decw_jan-89_to_nov-90

    
    They're still in VmsKit::Decw$Public:[X.Examples].  Talk to Paul
    (Star::) Steeves about giving this to cmp's and others.  There was a
    plan in the works but I don't know what became of it.  They could also
    try the Xscope (I think that's its name) program posted to
    comp.sources.x some weeks ago.  They should check an archive sight for
    availability.
    
    					monty

    
    
    Are there alternative sites ???
    
    I have tried to copy it from VMSKIT for 4 days now and I keep getting
    insufficient resources.  I have tried over the weekend and even
    late at night/early in the morning.
    
    Any pointer would be much appreciated.
    
    +Joe+
    

    
    Apparently, vmskit's disks are destroyed and there are no backups.  I
    have everything on decwin but you can't get there.  Anyone want to host
    a second decwindows public directory?
    
    					monty

    
    Ok, Andy Leslie has graciously provided some disk space and a home for
    these tools while vmskit does whatever it does.  They may be found in:
    
    		Leslie::Decw$Tools:
    
    along with the tcp/ip transport and xgethost.
    
    					monty

    To save poor Andy being flooded:
    also available in UFP::SYS$KITS:[DECW$TOOLS].
    	-Rick

    
    New, Improved Xwoodward!  Now with byte-swapping for all your SUN
    clients.  Well, maybe.  At least it works on ico.  Souce and
    executable are available in:
    
    	Vmskit::Decw$Public:[Unsupported]
    
    Not only does it byte swap but it is even slower than the previous
    versions.  Bug reports and suggestions cheerfully accepted.
    
    					monty

    
    do xliddy and xwoodward exist under Ultrix?

    No.  Last I heard, both were still VMS based.
    
    Note that if you have a VMS system, you could run XLiddy and
    XWoodward there and still test the Ultrix server and clients,
    theoretically.  
    
    
    John B.

    
    >Note that if you have a VMS system
    
    Well, how is the port to the DS3100 coming along?

Is there any update on the availability of XLIDDY on ULTRIX (specifically the
DS3100).  There is a problem I would like to track, however, I can't do it with
remote display, because the problem doesn't occur then.  It only occurs when the
executable displays to it's local machine.

Thanks,
Beth

    
    Paul Jensen posted an interesting program (Xpmon) that he is
    working on in the X Conference (RDVAX::X).
    
    The following is what Paul posted.  Go to that note to get pointers
    on how to get Xpmon.
    
    Kris.....
    
    ------------------------------
    
    Note 688.0         Xpmon: X protocol monitor
    RANCHO::JENSEN "Paul Jensen"
    
        The first reply to this note contains the man page to a program
        I hacked up to monitor the protocol stream between an X client
        and a server.
    
        Though this program is similar to (though developed without
        knowledge of) xscope, it offers the following advantages:
    
            (1) can monitor multiple clients
    
                 extensions by minor opcode
    
            (4) can forward to multiple servers (if clients link
                against modified Xlib).
        I am posting this here in hopes that some of the readers of
        this conference may find Xpmon useful.  It is still under
        semi-active development (read: midnight hack), and I expect
        it to become enhanced (particularly with regard to the
        data analysis tools) in the future.  If anyone would like to
        be informed of future releases, or make suggestions for
        improvements, they should send me mail at decwse::jensen.
    
        Regards,
    
                                            /Paul Jensen
    
        
    
    
    
    

I copied xliddy from MPGS.  The system I linked it on is VMS V5.1:

$ cc/define=no_tcp xliddy
$ link xliddy,getopt,clink/opt
$ xliddy -o liddy.log -s 0 -d 2 -w cecil (or cecil::)


Where clink/opt points to the C library.

I get the [Ready] message, then on an ULTRIX machine (DS 3100, UWS V2.1) I run
a GKS3D application (which has DECwindows as the device type).  The GKS3D
application is failing when it tries to connect to the server, and xliddy
fails with the following:

%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
(or %SYSTEM-F-IVDEVNAM, invalid device name )
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

XLIDDY          mailbox_read_ast                 2836      0000016C  00000F70
                                                           801588EF  801588EF
XLIDDY          main                             2766      00000310  00000D60


The log file is empty.  The node specified by -w is the node xliddy is running
on.  Am I doing something wrong?

    
    RE: .-1
    
    What is the display set to on your PMAX ??  I think it should be set
    to the node which xliddy is running on (cecil ??)
    
    Also do ALL nodes involved know about each other ????
    
    I've gotten something similar to your description to work...
    
    
    Good luck,
    
    
    /Joe
    

and set the server number to (in your case 2) the number specified in the
-d switch.  and use decnet transport.

> $ xliddy -o liddy.log -s 0 -d 2 -w cecil (or cecil::)
    
> The log file is empty.  The node specified by -w is the node xliddy is running
> on.  
    
    Is the real server on node CECIL?
    
    
    John B.

    
    I've been using a modified version of xliddy as a Record/playback
    mechanism for testing X applications.  The problem I have come
    across is when the user moves the window.  The X_Event I get is
    "non-core".  I've looked at the source and know understand why this is
    being reported...but can anyone suggest some ways to capture the events
    done when a user moves a window.  The output file created by Xwoodward
    looks like it has the right sequence number but it also reports some
    other stuff.  Could this somehow be sent to the client (or server) so 
    the window is moved automatically ??????
    
    
    Any ideas Monty ???????
    
    
    
    Thanks,
    
    
    /Joe G.
    
    

RE. .17

	Monty doesn't work for the company anymore.

							mike

    
    Anybody that's worked with XLIDDY have any ideas ????
    
    
    /jg
    

>>    can anyone suggest some ways to capture the events
>>    done when a user moves a window.

This should do it.  Pass the top level (shell) widget ID to
EnableMoveNotification, and the x and y variables will track the
window's actual location on the screen.  (Untested)

-steve-


/* There are a variety of window managers, but they all seem to send
 * a client message of one type or another to the client's top level
 * window whenever it is moved by the user.  (This is usually the window
 * belonging to a toolkit shell widget.) To play it completely safe,
 * treat ANY client message as a possible indication that we've moved. */

static x, y;		/* shell widget's location on screen */

static void GetWindowPosition(w)
    Widget w;
{
    Window tmpchild;

    XTranslateCoordinates (XtDisplay (w), XtWindow (w),
	RootWindowOfScreen (XtScreen (w)),
	-w->core.border_width, -w->core.border_width, &x, &y, &tmpchild);
}

static void HandleNonmaskableEvent(w, closure, eventP)
    Widget w;
    Opaque closure;
    XEvent *eventP;
{
    if (eventP->xany.type == ClientMessage) GetWindowPosition;
}

static void EnableMoveNotification(w)
    Widget w;
{
    /* Register an event handler for nonmaskable events.  In particular,
     * we are interested in client messages from the window manager. */

    XtAddRawEventHandler (w, 0, 1, HandleNonmaskableEvent, 0);
}