On Tuesday 10 June 2008 8:57:54 pm Neal Holtz wrote:
> It turns out that this made me realize I could easily modify
> the original c++ argb code to be equivalent, and it turns out
> that I do get exactly the same behviour with the c++ version.
> So therefore it is NOT a PyQt problem.
>
So I've ju
On Tuesday 10 June 2008 5:20:05 pm Benno Dielmann wrote:
> I think it's an X11 problem. Take a look at the comments to this blog entry:
>
> http://zrusin.blogspot.com/2006/10/argb-windows.html
>
> Other people have the same issues with the c++ version.
>
> By the way, I tried the argb.py you att
On Tuesday 10 June 2008 5:04:56 pm Phil Thompson wrote:
> On Tuesday 10 June 2008 9:52:18 pm Neal Holtz wrote:
> > Hi,
> >
> > IN the following program, if I run it with a '-visual TrueColor' option,
> > I get the following behaviour:
...
>
> What makes you think it's a PyQt problem?
>
Nothing i
I think it's an X11 problem. Take a look at the comments to this blog entry:
http://zrusin.blogspot.com/2006/10/argb-windows.html
Other people have the same issues with the c++ version.
By the way, I tried the argb.py you attached in one of your previous mails and
I don't get these errors.
Ben
On Tuesday 10 June 2008 9:52:18 pm Neal Holtz wrote:
> Hi,
>
> IN the following program, if I run it with a '-visual TrueColor' option,
> I get the following behaviour:
>
> When I move the mouse pointer into the window for the first
> time, I get:
>
> X Error: BadMatch (invalid parameter attributes
Hi,
IN the following program, if I run it with a '-visual TrueColor' option,
I get the following behaviour:
When I move the mouse pointer into the window for the first
time, I get:
X Error: BadMatch (invalid parameter attributes) 8
Extension:157 (RENDER)
Minor opcode: 4 (RenderCreatePict
