On Fri, 18 Nov 2011 10:01:05 +0100 Juan Jose Garcia-Ripoll <juanjose.garciarip...@googlemail.com> wrote:
> I am not sure what you mean by "not able to access the CLX functions". It > seems that your code was indeed able to call XLIB's functions. What is > shown above is a protocol error, am I wrong? As Matthew explained, it may > be due to CLX, but it might also be due to ECL corrupting the communication > (unlikely but possible). I will try with some other machine myself. It's indeed a protocol error, like if the message request was wrong or the like... Interesting for reference: My older message about it: http://www.mail-archive.com/ecls-list@lists.sourceforge.net/msg01145.html A 2008 thread about a similar problem: http://lists.common-lisp.net/pipermail/mcclim-devel/2008-January/006825.html Thanks, -- Matt ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
