Re: sampleFramework.SetKeyboardCallback
- From: "Zman" <zman@xxxxxxxxxxxxxx>
- Date: Wed, 12 Oct 2005 16:12:35 -0700
OK, this was bugging me and as you all know I don't have a job taking up my
time :-)
Looks like the mouse and keyboard callbacks were called from within
dxmut.cs->WindowsProcedure.
This appears to have been replaced with a single callback that handles all
of the WIndowsProcedure messages. So you need to hook the WndProcCallback
and do the mouse, keybaord and other message in there. See the SDK samples
they all have a line like this:
sampleFramework.SetWndProcCallback(new WndProcCallback(sample.OnMsgProc));
--
Zman (mailto:zman@xxxxxxxxxxxxxx)
http://www.thezbuffer.com
News and Resources for Managed DirectX
"Zman" <zman@xxxxxxxxxxxxxx> wrote in message
news:uuSraA4zFHA.908@xxxxxxxxxxxxxxxxxxxxxxx
> There is no help for the framework, its provided in source code so you
> won't find any.
>
> I took a quick look at the code. I suspect you have replaced the framework
> code from the book with the framework code from the SDK becuase as you are
> seeing, those methods don't exist. I would go back to the framework code
> that came with the book - they compile against the august DLLs if you
> download the patch.
>
> Off the top of my head I'm not sure what has replaced it in the newer
> frameworks. Becuase the frameworks are provided as source they are not
> really part of the main SDK so they tend to change a lot more.
>
> --
> Zman (mailto:zman@xxxxxxxxxxxxxx)
> http://www.thezbuffer.com
> News and Resources for Managed DirectX
>
>
> "Udo Schneider" <UdoSchneider@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:0E77963C-F193-4F58-BB51-5450D1C6AFAD@xxxxxxxxxxxxxxxx
>>
>>
>> "Zman" schrieb:
>>
>>> Toms book should work fine with the August SDK (though there are a
>>> couple of
>>> patches required - http://www.thezbuffer.com/articles/271.aspx)
>>>
>>> However I don't recall those being the changes. Did you make sure that
>>> the
>>> references you added were the right ones (you may have multiple)
>>> they should all be 2902, apart from D3DX which is 2907 (Aug), 2908 (Oct)
>>>
>>
>> Thanks for your answer. Yes, I made two references ("Microsoft.DirectX"
>> and
>> "Microsoft.DirectX.Direct3D" which have the Version 2902 and one
>> Reference
>> "Microsoft.DirectX.Direct3DX" which has the version 2907). The last one I
>> also tried with version 2905, but it's the same result.
>>
>> I just realized, that when I try to use the help (not the MSDE, but that
>> help
>> which has been integrated into VisualStudio 2003), then I see a topic in
>> the list, when I search for "Framework.SetKeyboardCallback". But when
>> I doubleclick that one, then instead of seeing the helptext to
>> "Framework.SetKeyboardCallback" I only see an errormessage which
>> states that no entry has been found under this index...:(
>> Might it be that my DirectX SDK is somehow corrupted???
>>
>
>
.
- Follow-Ups:
- Re: sampleFramework.SetKeyboardCallback
- From: Udo Schneider
- Re: sampleFramework.SetKeyboardCallback
- References:
- Re: sampleFramework.SetKeyboardCallback
- From: Zman
- Re: sampleFramework.SetKeyboardCallback
- From: Zman
- Re: sampleFramework.SetKeyboardCallback
- Prev by Date: Re: Getting started with EmptyProject
- Next by Date: RE: (Solution) Frustum Culling in C# / VB.NET
- Previous by thread: Re: sampleFramework.SetKeyboardCallback
- Next by thread: Re: sampleFramework.SetKeyboardCallback
- Index(es):
Relevant Pages
|
