Is ridiculously hard, and I’m hoping that this can get through.
I tried posting this to the forum earlier, but had to post it in the bug
tracker instead because of the stupid spam filter on here. However, I think I
would have a better chance of getting an answer if I had it on the forum, so
if you would please go here:
How am I supposed to use the debugger when the only thing it does is produce
that access violation at your function? And that’s the only one that doesn’t
work, as far as I can tell, except that GetMousePos doesn’t actually seem to
get the mouse position… Even if I move the callback functions to just after
the glfwInit and OpenWindow, it still only gives that stupid access violation,
and there’s no stack trace.
My program isn’t DOING anything except glfw initialization and opening a
window. And then registering those callbacks. If I’m not doing the functions
right, then please let me know. Anything other than a static declaration
doesn’t let me compile even. It’s corrupting memory when trying to REGISTER
that callback function.
When I used GLFW3, I built it, but I didn’t try any of the tests or examples.
I will download 2.7.6 source and try them, but I will emphasize (if not
again) that I am using strict C++, and so, since the examples are all C, they
are pretty much useless to me.
I suppose I could try converting my code over to C to see if it has any
problems, but that would be tedious, and I would guess it would work just fine
since you test it with C programs.
I also wanted to let you know that I went back and fixed my
SetWindowCloseCallback function so that it didn’t need the cast. The whole
program still compiles just fine (GLFW recognizes the MousePosCallback
function I have), but on running, it still has the access violation on
glfwSetMousePosCallback.
I don’t know what more I can say. I’ve given my best guesses as to what’s
wrong, suggested tools that may help you and asked questions that could have
helped you towards a solution.
I am, however, fairly certain that glfwSetMousePosCallback didn’t cause an
access violation on its own, based partly on it only using global data and
partly on the thousands of people who use it every day without this issue.
You’re welcome to read the few lines involved and verify this for yourself.