• 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
zppz

Config groups and object property accessors

4 posts in this topic

After creating an object type with RegisterObjectType, I want to let the users of my program dynamically add and remove properties for the object type, and also let them access the properties with the convenient .xxx style of coding.

 

So I use RegisterObjectMethod to create the necessary get_xxx and set_xxx functions, and everything works great. To make this easily reversible later, I enclose it in a BeginConfigGroup/EndConfigGroup.

 

The trouble is, using RemoveConfigGroup after this does not seem to remove these object methods. No errors or other problems occur, but the get_xxx/set_xxx functions remain as if they had not been removed, and can happily be used still.

 

The same RegisterObjectMethod procedure can then be repeated, also with no errors, but this seems to cause a duplicate of the functions to be registered, so that scripts fail to compile with the message "Found multiple get accessors for property 'xxx'"

 

Just wondering if this is the expected behavior. And if so, is there a better way to do what I'm trying to do... thanks!

0

Share this post


Link to post
Share on other sites

It's currently not possible to register only part of an object type in a separate configuration group. Methods, properties, and behaviours will be placed in the same group that was used when RegisterObjectType() was called. To do what you want you need to put the full object type in the configuration group, and then re-register it as a whole when exchanging the properties.

 

Unfortunately this is not clear in the manual. I'll have to update the manual to make this clear.

 

I'll also add to my to-do list to investigate the possibility to add the support for registering parts of types in different modules. 

 

 

When registering methods AngelScript checks for duplicates. The problem here is that you're registering the virtual property with a different type, so it will be seen as a method overload rather than a duplicate method. The get_ method should have given an error though, as it is not possible to overload a method with just a difference in the return type.

0

Share this post


Link to post
Share on other sites

Thanks Andreas.

 

After a while I came to realize that I need separate script engines. Many object types refer to each other so they need to be in the same config group, which cascaded into basically replacing everything anyway. Another reason is that I want to keep these property settings separate for different documents in the workspace, even when the object type names are the same. For example the user could have two documents open, and in one of them the 'body' class could be given a 'xxx' property, without giving that property to the 'body' class in the other document.

 

Plus, coding-wise it was somewhat easier and less error-prone to simply drop everything and create it afresh. Luckily I don't need to keep any persistent state (global variables etc) in the script engine itself, so I could do this :)

 

Keep up the good work!

0

Share this post


Link to post
Share on other sites

Have you looked in to access masks?

 

With these you'll be able to use a single engine instance and expose different interfaces to different scripts. I'm not sure this is exactly what you're trying to do, but if you haven't seen this feature yet, it may be worth looking in to.

0

Share this post


Link to post
Share on other sites

I did notice the access mask feature, but I did not look into them much because using separate engines worked ok and did not require any managing of masks for each document that the user might open.

0

Share this post


Link to post
Share on other sites

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
Sign in to follow this  
Followers 0