• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
  • entries
    17
  • comments
    21
  • views
    17199

C# Annoyances Issue 1: No Macros

Sign in to follow this  
Followers 0
Kwizatz

272 views

C# has no macros, this was made on purpose, however, I found a place where I could really use them.

I am writing a "Settings" class that uses XML Serialization, I need to use System.Drawing.Color variables which apparently do not serialize "out of the box", so a proxy string setter/getter needs to be made, and so the class is written (this is for a level editor):


public class Settings
{
private System.Drawing.Color gridPrimaryColor;
private System.Drawing.Color gridSecondaryColor;
private System.Drawing.Color gridTertiaryColor;
private System.Drawing.Color viewBackgroundColor;
[XmlIgnoreAttribute()]
public System.Drawing.Color GridPrimaryColor
{
set
{
gridPrimaryColor = value;
}
get
{
return gridPrimaryColor;
}
}
[XmlIgnoreAttribute()]
public System.Drawing.Color GridSecondaryColor
{
set
{
gridSecondaryColor = value;
}
get
{
return gridSecondaryColor;
}
}
[XmlIgnoreAttribute()]
public System.Drawing.Color GridTertiaryColor
{
set
{
gridTertiaryColor = value;
}
get
{
return gridTertiaryColor;
}
}
[XmlIgnoreAttribute()]
public System.Drawing.Color ViewBackgroundColor
{
set
{
viewBackgroundColor = value;
}
get
{
return viewBackgroundColor;
}
}
[XmlElement("GridPrimaryColor")]
public string HTMLGridPrimaryColor
{
set
{
gridPrimaryColor = ColorTranslator.FromHtml(value);
}
get
{
return ColorTranslator.ToHtml(gridPrimaryColor);
}
}
[XmlElement("GridSecondaryColor")]
public string HTMLGridSecondaryColor
{
set
{
gridSecondaryColor = ColorTranslator.FromHtml(value);
}
get
{
return gridSecondaryColor;
}
}
[XmlElement("GridTertiaryColor")]
public string HTMLGridTertiaryColor
{
set
{
gridTertiaryColor = ColorTranslator.FromHtml(value);
}
get
{
return gridTertiaryColor;
}
}
[XmlElement("ViewBackgroundColor")]
public string HTMLViewBackgroundColor
{
set
{
viewBackgroundColor = ColorTranslator.FromHtml(value);
}
get
{
return viewBackgroundColor;
}
}
}




Now thats a lot of code!, its there just to make a point, which is "there will be a lot of identically defined variables differing in name only".

Lets extract the code for a single variable:


private System.Drawing.Color viewBackgroundColor;
[XmlIgnoreAttribute()]
public System.Drawing.Color ViewBackgroundColor
{
set
{
viewBackgroundColor = value;
}
get
{
return viewBackgroundColor;
}
}
[XmlElement("ViewBackgroundColor")]
public string HTMLViewBackgroundColor
{
set
{
viewBackgroundColor = ColorTranslator.FromHtml(value);
}
get
{
return viewBackgroundColor;
}
}





Now, thats what it takes to define a single property variable thats serializable, wouldn't you just love to have the power of macros and do this (backslashes removed because of formating):


#define XMLITEM(INTERNAL,EXTERNAL)
private System.Drawing.Color INTERNAL;
[XmlIgnoreAttribute()]
public System.Drawing.Color EXTERNAL
{
set
{
INTERNAL = value;
}
get
{
return INTERNAL;
}
}
[XmlElement("EXTERNAL")]
public string HTMLEXTERNAL
{
set
{
INTERNAL = ColorTranslator.FromHtml(value);
}
get
{
return INTERNAL;
}
}



and then just


public class Settings
{
XMLITEM(gridPrimaryColor)
XMLITEM(gridSecondaryColor)
XMLITEM(gridTertiaryColor)
XMLITEM(viewBackgroundColor)
}





I would.

Macros are prone to abuse, but they do have their uses.

0
Sign in to follow this  
Followers 0


2 Comments


off the top of my head can you not serialize a class in c# like so:

[Serializable]
class someClass()
{
...
}

whether that would work for XML serialization i don't know suppose you could try:

[XMLSerializable]
class someClass()
{
...
}

just for kicks. seems daft that they make you go through so much trouble
0

Share this comment


Link to comment
I am a C# newbie coming from a C/C++ background, so I am not sure you completely have to go through all that, but from my Google research it seems so, apparently the problem stems from C# not being able or not having a default way to serialize binary variables.

I actually had to add the [Serializable] tag in order for the code to work, without it the xml items were written as having no data.
0

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now