Should I learn .NET for making design tools?
Members - Reputation: 976
Posted 08 July 2012 - 03:49 PM
The most practical example is being able to use .net's PropertyGrid with any object in the game with minimal effort, but has been taken much much further into providing editors for various parts of gameplay, and writing custom data viewers. The binding of the .net libraries was done using managed c++ solely so the dll could have unmanaged exports, but every other tool library we write is in C#.
Crossbones+ - Reputation: 3879
Posted 19 July 2012 - 03:05 PM
As for what kinds of tools I'm looking to develop, I finished the editor tool and moved the project out of beta. I posted it in the 'breaking in' forum asking for advice about making it acceptable for a portfolio project.
Here be the thread, if you wanna peek at the tools. In the solution they're the 'rpak' and 'stage editor' projects.
It's not really the difficulty of working with GDI in terms of not understanding it or something. It's just the overwhelming rectal discomfort caused by managing it. I was actually thinking of making a GDI wrapper class, but I'll check out some of the ones mentioned first.
Thank you everyone!
There are ten kinds of people in this world: those who understand binary and those who don't.
Crossbones+ - Reputation: 6804
Posted 19 July 2012 - 04:54 PM
It's not really the difficulty of working with GDI in terms of not understanding it or something. It's just the overwhelming rectal discomfort caused by managing it.
Thats the main reason for all the alternative GUI libraries out there to exist(and quite alot of other libraries aswell), Win32 isn't difficult, it is tedious and timeconsuming and that really is far worse than being difficult. (Things that are difficult become easier as your skills improve, the tedious and timeconsuming things however remains tedious and timeconsuming forever)
The voices in my head may not be real, but they have some good ideas!