So I checked the framework and tried to understand how the keybaord/mouse interaction worked.
So basically the framework registered a message loop in HandleMsg try to pool what message is coming in. So a completely new mouse/keyboard class is wrapped.
I found the DirectXTK has the mouse/keyboard class, why not use this? Just curious. I mean, the Microsoft has already done the work.
https://github.com/Microsoft/DirectXTK/wiki/Keyboard
Why does not the framework use DirectXTK for mouse/keyboard?
-
- Posts: 1
- Joined: December 28th, 2018, 11:33 am
-
- Posts: 4373
- Joined: February 28th, 2013, 3:23 am
- Location: Oklahoma, United States
Re: Why does not the framework use DirectXTK for mouse/keybo
In the chili framework, there is a mouse and keyboard class, but each class has an Event class that get's cached, not the whole mouse and keyboard instance.
The idea for the framework was to avoid having to rely on 3rd party ( not apart of the standard library or Windows SDK ) thus making it easier for beginners learning C++ to use.
The idea for the framework was to avoid having to rely on 3rd party ( not apart of the standard library or Windows SDK ) thus making it easier for beginners learning C++ to use.
If you think paging some data from disk into RAM is slow, try paging it into a simian cerebrum over a pair of optical nerves. - gameprogrammingpatterns.com