Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


wisey

Member Since 21 Feb 2009
Offline Last Active Nov 23 2013 06:01 PM

Posts I've Made

In Topic: learning vc++/directx

23 July 2013 - 04:59 PM

Thanks for your replies so far. I also sent a message to somebody working for Ubisoft but he seems to be ignoring every attempt I have made to contact him. Obviously, I would prefer to get advice from a professional so special thanks goes out to Jason Z. 

 

I am going to wait a little longer before I decide how to spend the next year of my life. 

 

--

Steve


In Topic: Input

26 June 2012 - 10:03 AM

Somebody in irc said that there's no replies because this is a boring topic field. But i'm quite stuck with this problem. Please help. I understand that it might be my c++ skills that are lacking.

--
Wisey

In Topic: Keyboard and Mouse Input

14 June 2012 - 04:36 PM

Oh thanks Washu

I didn't know you could google the error's like that, thanks. So the first link told me to add some braces which solved the error but now I have more errors.

http://ideone.com/bRN80

So this time I tried googling error C2146 and error C4430 and it didn't really help. There is nothing wrong with the code asaik but i'm probably missing something. Without showing you my entire code base I realize you may struggle to help me.

But I know that some of you guys are very good at reading the output from a compiler. For instance, I used to just copy and paste entire lines from the output. When just the error code will suffice. So I don't know, maybe you can help.

Thanks

--
Wisey

In Topic: WM_KEYDOWN and WM_KEYUP

20 May 2012 - 02:22 PM

You forgot a break.



Thanks tomalak

It works with the break.

--
Wisey

In Topic: WM_KEYDOWN and WM_KEYUP

20 May 2012 - 01:17 PM

It looks like in main that WM_KEYUP is being fired off and the values changed even though the key hasn't been released. I working this out by commenting out the lines where the bool's are being set on a key press. If I do this the mode doesn't change.

Any idea's why WM_KEYUP is being fired as soon as the key is pressed inwards?

--
Wisey

PARTNERS