bug-xnee
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-xnee] Re: xnee and synchronisation


From: Henrik Sandklef
Subject: [Bug-xnee] Re: xnee and synchronisation
Date: Mon, 09 Jan 2006 23:59:39 +0100

On Mon, 2005-11-07 at 16:05 +1100, Serg Belokamen wrote:

> Assuming I have initial Xnee session with everything I need. Now, I want 
> to be able to check for availablity of that MySQL app. So can Xnee 
> access it or not... For example, if it was moved from previous directory 
> or removed all together.

Xnee can fake events (from different input sources). That's it. 

"Xnee is a suite of programs that can record, replay and distribute user
actions under the X11 environment. Think of it as a robot that can
imitate the job you just did."

> Also, to have the ability to check the returned data and compare that to 
> first "correct" Xnee session and abort of the screens are different (for 
> example different values in text fields or labels).

What returned data? From a MySQL session. That is up to you to check.
Not Xnee.

Comparing snapshot is another thing:
 http://savannah.gnu.org/support/?func=detailitem&item_id=103871

> So that that, I have tried using ranges. Infact I attempted to use 
> complete range, and few selected once... No luck. Also tried using 
> thresholds but that didn't do much either.

For more info on what data to use in your ranges, 
  read chapter 7 "Xnee internals"

You always use thresholds, they have default values.

Since I do not know what type of toolkit you are using (saying GUI based
gives us no clue at all). But this is tricky. You have to analyse your
apllication's request(Xlib calls) and set ranges to fit the application.

One way to do this is to:
  cnee --record -hp --event-range 2-31

You'll see many NoExpose (Nr 14) being recorded, exclude them
  cnee --record -hp --event-range 2-13,15-31

Keep excluding data like this until you find a setting that spits out
data when you do something interesting with your application.


> Problem is not that I dont know what ranges to use (I dont, but...) but 
> rather that I dont understand how to synchronise

Again, read chapter 7.

>  or how it works simply 
> because all of the documentation is quiet outdated.

Ok, what docs are you looking at? Xnee? RECORD? It is kind of hard to
know what you are refering to when saying so! Just because a document is
old doesn't mean it is not valid. 

/hesa

>    Regards,
>       Serg
> 
> Henrik Sandklef wrote:
> 
> >Hi
> >
> >thanks for your report.
> >... please use bug-xnee list instead (see CC).
> >
> >(I crosspost to info-xnee to show we are switching to bug-xnee)
> >
> >
> >On Wed, 2005-11-02 at 16:50 +1100, Serg Belokamen wrote:
> >  
> >
> >>I am having an issue synchronising Xnee.
> >>
> >>Assume I have a recorded a session:
> >>
> >>xterm
> >><NEW WINDOW OPENED>
> >>ping -n 5 HOST
> >>ls -al
> >>......
> >>Is there a way to monitor those events. For example, take an alternative 
> >>course of action if instead of expected "data input" we get an error 
> >>dialog or anything else that is not expected.
> >>    
> >>
> >
> >There are two questions here, isn't it?
> >
> >1) Is there a way to monitor/record this?
> >Yes, there is. I am not sure which requests you have to record but you
> >can find out yourself. Easiest way is probably 
> > in xterm nr 1:   sleep 5 ; ls -l 
> >
> > in xterm nr 2): cnee --record --request-range <tour range goes here>
> >
> >until you find something useful to use to sync with. It would be great
> >if you could send us the names of the requests you will use.
> >
> >
> >2) Take an alternative path?
> >Xnee can (today) take no alt. path. DOes that answer your question?
> >Can you explain a bit more what it is you'd like to do.
> >
> >
> >/h
> >
> >
> >  
> >
> 
> 
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]