If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register or Login
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

If "inst" is not NULL, then debug into the Move() function. Can you do that? If you can, where does the debugger take you? Does it actually go into a function, or does the debugger take you to some weird address that makes no sense? If it is the latter, this means that inst->Move points to garbage.

Re: [win32] - creating controls using class's

Where's the declaration/definition of move()?

All advice is offered in good faith only. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/

If "inst" is not NULL, then debug into the Move() function. Can you do that? If you can, where does the debugger take you? Does it actually go into a function, or does the debugger take you to some weird address that makes no sense? If it is the latter, this means that inst->Move points to garbage.

Re: [win32] - creating controls using class's

event(Move,(int x, int y));

????????? As a definition of the class function Move()

All advice is offered in good faith only. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/

Re: [win32] - creating controls using class's

Originally Posted by Cambalinho

but...

The point being is that you should always check return codes. It doesn't matter if you are confident that it will work -- you always check return values if the function says what is returned on failure (or success).

The other reason is that we are looking at your code -- there is no way we can tell if the call worked or not. An explicit check for the return value not only helps you, it helps others looking at your code.

All advice is offered in good faith only. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/

Re: [win32] - creating controls using class's

Originally Posted by Paul McKenzie

The point being is that you should always check return codes. It doesn't matter if you are confident that it will work -- you always check return values if the function says what is returned on failure (or success).

The other reason is that we are looking at your code -- there is no way we can tell if the call worked or not. An explicit check for the return value not only helps you, it helps others looking at your code.

Regards,

Paul McKenzie

thanks for all my friend.
i will continue with these thread open, until complete these class. thanks for all

All advice is offered in good faith only. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/