ollydbg

Results 285 comments of ollydbg

I'm on Windows too. I also see such ~~~~ Couldn't find 'HEAD' ~~~~ Error. But after adding the option `--no-blob-protection`, this error is gone. Hope this helps, but I'm still...

![rotation_error](https://user-images.githubusercontent.com/561818/126165922-7b6422e1-a4b3-4b1e-9740-0f9e8f5c395e.gif) I have upload the screen cast gif of the rotation, I just use the left key drag horizontally. Note that the code is 1:1 map from the code: [MouseInteractionExample.cpp](https://github.com/mosra/magnum-examples/blob/master/src/mouseinteraction/MouseInteractionExample.cpp)...

Hi, I just try the base-wxwidgets project under Code::Blocks (I'm using msys2's prebuild magnum library, and msys2's wx 3.1.5 library) The pure base-wxwidgets works OK without any issue. See the...

Some extra information, if I enable the console window, I see when it crashed, some message was shown in the console, see below image show: `GL::Context::current(): no current context` ![crash2](https://user-images.githubusercontent.com/561818/125899676-31ad4e34-b837-45f8-b040-958c7f8d42af.png)...

By searching the error message, I got this: [Context::current(): no current context · Issue #167 · mosra/magnum](https://github.com/mosra/magnum/issues/167) As the internal context is created by the `NoCreate` parameter. ~~~~ _glContext{NoCreate, argc,...

I solved this issue by a hack that I just create a function to initialize the `_glContext` member variable before the other shader and mesh members, see the full code...

Hi, @mosra , many thanks! The document: [in the OpenGL wrapper overview](https://doc.magnum.graphics/magnum/opengl-wrapping.html#opengl-wrapping-instances-nocreate) is so nice, especially for the beginners.

My idea is: it is not possible to use the OS's Native Text input control. To implement(simulate) this feature, you have to capture the keyboard input, and print the character...

> This is likely related to #55, but perhaps there's more going on as I think that issue was fixed, and the versions/symptoms reported above don't line up exactly. >...

> This is likely related to #55, but perhaps there's more going on as I think that issue was fixed, and the versions/symptoms reported above don't line up exactly. >...