8 Commits

Author SHA1 Message Date
Konstantin Koch
8287c54432 Included the Visual Studio extension and made the necessary changes to make it run.
Replaced the old VS templates with ones that offer more flexiblity.
Started replacing the Content Project for the samples with our custom project type.
Inlcuded a basic not yet working AssimpImporter.
2015-04-08 14:50:03 +02:00
Glatzemann
a5f4931578 fixed issue #1082 (SpriteFont UTF8 issue) 2015-03-15 01:12:10 +01:00
SND\eagleeyestudios_cp
a56e950056 Content Pipeline:
Fixed SpriteFont Building (Importer/Processor). It now renders fine in the TextRendering Sample.
2015-03-15 01:12:05 +01:00
Glatzemann
2eb7923339 - fixed reading of SpriteFont's (DefaultCharacter handling was wrong)
- fixed handling of DefaultCharacter in FontDescriptionImporter (no handling)
- set DefaultCharacter in SampleContent's Debug font
2015-03-15 01:12:02 +01:00
SND\eagleeyestudios_cp
c316436f32 Content Pipeline:
- Fixed a Bug in FontDescriptionImporter
- Removed Debugger.Break() in XmlImporter
2015-03-15 01:12:01 +01:00
SND\eagleeyestudios_cp
3c5e98b783 Content Pipeline:
- Implemented important features of the FontDescriptionImporter. Importer works now, but still needs some (optional) features
- Fixed some bugs in the FontDescriptionProcessor. Building now works to the point where the ContentCompiler wants a generic writer instance
2015-03-15 01:11:57 +01:00
SND\eagleeyestudios_cp
d7bd5b7018 Content Pipeline:
- Corrected private setter in FontDescription. If the importer can not set that value, its pretty useless.
- Implemented more of the FontDescriptionImporter. Can not progress further, because it seems there is no manged solution of getting a font's characters
- added missing copyright texts and regions FontDescriptionImporter.cs and FontDescriptionProcessor.cs
2015-03-15 01:11:54 +01:00
SND\eagleeyestudios_cp
72ee0fd837 Content Pipeline:
- implemented FontDescriptionProcessor
- began implementing FontDescriptionImporter
2015-03-15 01:11:52 +01:00