I am not sure if this is an expected behaviour or not yet ported to
Python 3.x , but when using glGetUniformBlockIndex
with uniformBlockName = "mymat" it throws an error:
baseplatform.py", line 385, in __call__
return self( *args, **named )
ctypes.ArgumentError: argument 2: <class 'TypeError'>: from_param() takes 2
positional arguments but 3 were given
I have to use uniformBlockName = b"mymat" instead.
I guess it it is the same with
window = glutCreateWindow(b"myWindow")
If this is what I think it is, I have noticed similar behavior for other
low-level shader-string-affecting calls.
I think doing it this way is probably the Right Thing, as I expect it
avoids needing to do direct string conversion to ASCII text.
From: Mike C. Fletcher <mcfletch@vr...> - 2014-04-01 17:56:07
On 14-04-01 01:46 AM, Walter White wrote:
> I am not sure if this is an expected behaviour or not yet ported to
> Python 3.x , but when using glGetUniformBlockIndex
This was a generic problem with unicode-parameter handling for
GLcharArray data-types. There were two issues, the first was that Array
Data Types were not allowing an extra parameter, the second was that the
Unicode format handler wasn't correctly calling the Bytes format handler
once it had converted the value. bzr head should make the code work, but
I'd like to track down *why* the from_param is getting an extra
argument, as I don't know why that would be present.
Mike C. Fletcher
Designer, VR Plumber, Coder
Get latest updates about Open Source Projects, Conferences and News.