Will look into the problemos asap. The bug we found is gone, so we're
now facing a new one. If that's better or worse I don't know......
> Thanks! I'll give it a shot this week for sure.
>
> James
>
> -----Original Message-----
> From: Henrik Sandklef [mailto:
hesa@...]
> Sent: Monday, April 20, 2009 5:01 AM
> To: Burke, James
> Subject: Re: [Bug-xnee] Re: XNEE problems / Questions
>
> Arhhhmmmgggh,
>
> i've missed this email. It's fixed. Found some spare hours. The
> solution was trivial, finding the bug was painful ;)
>
> /hesa - in preps for 3.03
>
>
>
> Burke, James wrote:
>> Hi Henrik - Any update on the synchronization problems?
>>
>> Do you think it would be possible to capture the necessary events during a 30 minute automated benchmark run that would allow for synchronization and subsequent replay?
>>
>> Thanks.
>> James
>>
>> -----Original Message-----
>> From: Henrik Sandklef [mailto:
hesa@...]
>> Sent: Tuesday, February 24, 2009 6:39 PM
>> To: Burke, James
>> Subject: Re: [Bug-xnee] Re: XNEE problems / Questions
>>
>> Burke, James wrote:
>>> Henrik - Thank you. I'm just coming aboard to the open source train.
>> I prefer the term Free Software :)
>>
>>
>>> I'll dig into CVS but if you can provide a link, it would be much appreciated.
>> Here are a link to nightly tar balls:
>>
>>
http://itupw056.itu.chalmers.se/xnee/nightly-tar-ball/>>
>> With these, you don't need to start by downloading from CVS. The tar
>> balls above are like "normal" releases, but from CVS HEAD.
>>
>>> I still have problems with synchronization. Part of my requirement is to be able to run the same recorded mouse/keyboard events at different processor speeds. I still have a few things to try.
>> I am still in thinking mode for that bug
>>
>>> Thanks.
>>> James
>>>
>>> -----Original Message-----
>>> From: Henrik Sandklef [mailto:
hesa@...]
>>> Sent: Monday, February 23, 2009 4:57 PM
>>> To: Burke, James
>>> Cc:
bug-xnee@...
>>> Subject: Re: [Bug-xnee] Re: XNEE problems / Questions
>>>
>>> This is now solved in CVS head.
>>>
>>> A script now can look like this:
>>>
>>> #!/bin/bash
>>>
>>>
>>> . /opt/xnee/latest/share/xnee/xnee.sh
>>>
>>>
>>> xnee_fake_key l
>>> xnee_fake_key s
>>> xnee_fake_key Return
>>>
>>>
>>> xnee_fake_key p
>>> xnee_fake_key s
>>> xnee_fake_key XK_space
>>> xnee_fake_key a
>>> xnee_fake_key u
>>> xnee_fake_key x
>>> xnee_fake_key w
>>> xnee_fake_key Return
>>>
>>>
>>>
>>>
>>>
>>> Henrik Sandklef wrote:
>>>> Burke, James wrote:
>>>>
>>>>>> Shell problem:
>>>>>> I followed the example in section "5.8 Shell scripts using Xnee" of
>>>>>> the xnee manual. Part of that example included xnee_fake_key calls:
>>>>>> Xnee_fake_key l
>>>>>> Xnee_fake_key s
>>>>>> Xnee_fake_key XK_Return
>>>>> Try "Return" (and not XK_Return) ......
>>>>>
>>>>> Does it work, then one of us has made a woops in the docs.
>>>>>
>>>>> JB - No, Return did not fix the problem.
>>>> Strange, works here.
>>>>
>>>>>> When I run the script, only the "l" gets outputted - the "s" and the
>>>>>> return do not.
>>>>>> I found that if I insert a "xnee_init_file" right before each
>>>>>> "xnee_fake_key" call, it works.
>>>>> The example and the bash file you're sourcing states you must call the
>>>>> init function.
>>>>>
>>>>> JB - I do call "xnee_init_file" at the start of the script:
>>>>> JB - #!/bin/bash
>>>>> JB - . ~/jpburke/xnee_code/xnee-3.02/share/xnee.sh
>>>>> JB -
>>>>> JB - xnee_init_file
>>>>> JB - sleep 1
>>>>> JB - xnee_fake_key l
>>>>> JB - xnee_fake_key s
>>>>> JB - xnee_fake_key Return
>>>>> JB - sleep 1
>>>>> JB - xnee_close_down
>>>>> JB - JB - As executed above, I only get the "l" output. If I insert an
>>>>> xnee_init_file
>>>>> JB - call before each xnee_fake_key call then it works as intended -
>>>>> "ls" and
>>>>> JB - return is typed in my xterm and a listing of files in the current
>>>>> directory
>>>>> JB - is displayed.
>>>> odd ..... yet crappy
>>>>
>>>>
>>>> Will have a look ... but after the other bug is fixed.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Bug-xnee mailing list
>>>>
Bug-xnee@...
>>>>
http://lists.gnu.org/mailman/listinfo/bug-xnee>>>>
>>
>
>