Rainweaver.Common Library (.NET)

[Raine]

Rainweaver.Common Library - .NET 3.5

Note
The library is not finished as of now, however you can still reuse
the structures contained.

Features
The Rainweaver.Common library contains an Input Manager, some commonly used
structures and a simple class containing two extension methods to store and
restore render surfaces.

InputManager
Call InputManager.Initialize supplying your render/main form, then attach
your events to the delegates you can find under the Rainweaver.Common.InputManager
class. Remember to Terminate the InputManager once you're about to close
your application. Check also the Mouse and Keyboard class.
Remember that right now you cannot change the form you're hooking to once it's set.

Structures
Some structures I've used for Darkmana and my user interface. They're inspired
by the .NET BCL, the main difference is that they use System.Single instead of
System.Int. You will find Rect, UVCoords, Point, Insets and Size. Common operators
and methods are already included. They're fairly self-describing, besides the
Rect.Scale method, which is a mysterious entity.

RenderSurfaceManager
Initialize the RenderSurfaceManager only if you mean to use the Store and Restore
extension methods, which you can use with TVRenderSurfaces.

Known Bugs
I have finished writing the input manager today and I'm sure I've missed something
here and there, either last minute bugs or things I've completely overlooked.
Please either PM me on the TV3D forums (RaineC) or post in the library thread.
Feedback and constructive criticism are always appreciated.

License
This library is free for commercial use. If you use the library, credits to me (Roberto Collina) would be nice and appreciated.

Download link: http://www.mediafire.com/?z03vd2suen1

[Zaknafein]

D'oh! .NET 3.5... I still use 2.0!
But I did take a look at it in the ol' Reflector and it looks nice.
You just taught me that these latest .NET versions have implicit fields when you make a property, that's awesome!

The mouse management looks very complete too. I'll give it a try once I finally decide to jump to VS2008.

[Brac]

D'oh! .NET 3.5... I still use 2.0!
But I did take a look at it in the ol' Reflector and it looks nice.
You just taught me that these latest .NET versions have implicit fields when you make a property, that's awesome!

The mouse management looks very complete too. I'll give it a try once I finally decide to jump to VS2008.

Implicit fields, anonymous classes, extension methods, linq!!! (fast queries on any IEnumerable, yumm)...
3.5 has potential, check it out zak (vs2008 is pretty too)

[Raine]

I find myself using a lot of lambda expressions... 3.5 is beyond cool.

D'oh! .NET 3.5... I still use 2.0!
But I did take a look at it in the ol' Reflector and it looks nice.
You just taught me that these latest .NET versions have implicit fields when you make a property, that's awesome!

The mouse management looks very complete too. I'll give it a try once I finally decide to jump to VS2008.

Well, I think the best part is the keyboard management, you get localized chars, making user input so much easier.

It's nothing special anyway, it's just taking the WndProc, hijacking it, handling WM_ messages, and spamming events.

Edit: Just realized some events aren't fired, I'll update this asap.

[324]

Does RenderSurfaceManager supports multi-threading(would be awesome)?
When you try to use two render surfaces in separated threads simultaneously TV crashes?

[Raine]

I might make it thread safe but rendersurfaces are inherently not thread safe. I for one advise against that, unless you're sure that no other rendering operations happen in a different thread.

[Zaknafein]

Indeed, the problem is not with rendersurfaces, it's with rendering at all. You can't ask the hardware to render in two contexts at the same time, every rendering operation must be mutually exclusive.

[324]

Yes, you are both right. How difficult is this to be implemented although?