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

Spawning coroutines from script and providing params

6 posts in this topic

(To follow up on http://www.gamedev.net/topic/591814-funcdefs-to-member-functions/ and http://www.gamedev.net/topic/607706-lambda-functions/ and http://www.angelcode.com/angelscript/sdk/docs/manual/doc_adv_coroutine.html ...)

 

I'm wondering how to allow a script to spawn a coroutine where the function signature (of the function to call in the newly-spawned script context) is not fixed/known ahead of time (and provide those parameters).

 

 

Using the script funcdef syntax, a script can create a function handle to a function-signature that I can't anticipate ahead of time. I'd like the script to then be able to spawn a coroutine using that handle as the starting point, and provide whatever params that function needs.

 

Is there any precedent for doing this? Or is it best to limit the script-side spawning of coroutines to a function signature that takes no params, or predefined-ahead-of-time number/type of params?

 

Thank you.

Edited by iraxef
0

Share this post


Link to post
Share on other sites

My recommendation is to design it so that the co-routine can take a dictionary. This way the script can pass any information it wants to the co-routine without the need for the application to have any knowledge of whatever the script wants to pass to the co-routine.

 

With the newly implemented support for initialization lists in the dictionaries the syntax doesn't become too weird for the script writer either. biggrin.png

 

void MyCoRoutine(dictionary @dict)
{
   ... do some processing as a co-routine
}
 
void main()
{
   dictionary values = {{'first', 1}, {'second', 2}, {'third', 3}, {'etc', 4}};
   SpawnCoRoutine(MyCoRoutine, values);
}
0

Share this post


Link to post
Share on other sites

That seems really elegant... I'll have to investigate (I'm not using the dictionary add_on quite yet)!

 

Thank you very much.

0

Share this post


Link to post
Share on other sites

I've created a CScriptDictionary object in C++, filled it in with some elements, and called script with that param.. and was able to print out all the dictionary keys.

 

Is there any guidance in the documentation which would be helpful as to the type id to use for this CScriptDictionary signature?

void Set(const std::string &key, void *value, int typeId);

So far I used asTYPEID_SCRIPTOBJECT when passing an std::string& to a script string (registered with the add_on), and asTYPEID_APPOBJECT when passing a void* to an application object registered as a reference type with script. Is that correct? Would I use asTYPEID_OBJHANDLE in any situation?

 

Thank you very much.

Edited by iraxef
0

Share this post


Link to post
Share on other sites
No, that isn't the way it works. Except for the built-in primitive types no types have a specific type id that can be determined before hand.

The only way of getting the correct type id is by querying the engine for it. You can GetTypeIdByDecl on the asIScriptEngine for application registered types, and the same method on the asIScriptModule for script declared types.

The asTYPEID_ flags can be used as bit masks on the typeid to get limited information on the type it represents.

Regards,
Andreas
0

Share this post


Link to post
Share on other sites

I got the below working, but it appears that if the dictionary (that's passed to the coroutine) contains some application-defined value types, modifying the value type in the dictionary in the coroutine affects the dictionary that was passed into MyCoRoutine() once SpawnCoRoutine() returns.

 

Before I execute "MyCoRoutine" from C++, I probably have to manually create a 2nd CScriptDictionary instance, fill it in element-by-element (creating copies of application-registered value types), and pass that instance to MyCoRoutine?

 

 

 


 
void MyCoRoutine(dictionary @dict)
{
   ... do some processing as a co-routine
}
 
void main()
{
   dictionary values = {{'first', 1}, {'second', 2}, {'third', 3}, {'etc', 4}};
   SpawnCoRoutine(MyCoRoutine, values);
}
Edited by iraxef
0

Share this post


Link to post
Share on other sites

If you absolutely do not want the co-routine to modify the original dictionary, then you'll need to do what you say, i.e. do a manual deep copy of the dictionary and all its values.

 

However, are you sure you need this? Perhaps you can instead take advantage of allowing the co-routine to modify the original dictionary to return values, or even allowing the caller to add extra information for the co-routine afterwards. 

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