Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

AppGameKit Classic Chat / UDT field limit?

Author
Message
mindsclay
12
Years of Service
User Offline
Joined: 1st May 2012
Location: Rocklin, CA, USA
Posted: 10th Oct 2013 01:27
Does anyone know the limit to the number of fields that can be assigned in a UDT?

Or perhaps the complexity of UDTs inside a UDT?

www.mindsclay.com
lucifermagus.mindsclay.com (not working with Firefox)
Auger
12
Years of Service
User Offline
Joined: 21st Aug 2011
Location: Out There
Posted: 10th Oct 2013 03:13
If I remeber corectly its 9. Someone can correct me if I'm wrong
mindsclay
12
Years of Service
User Offline
Joined: 1st May 2012
Location: Rocklin, CA, USA
Posted: 10th Oct 2013 03:20
The field I deleted from the UDT was #9, but it was itself a UDT.

I think I just overloaded it, but was wondering the official limits.

www.mindsclay.com
lucifermagus.mindsclay.com (not working with Firefox)
Digital Awakening
AGK Developer
21
Years of Service
User Offline
Joined: 27th Aug 2002
Location: Sweden
Posted: 10th Oct 2013 08:14
Not sure there are any limits. My largest is 35. I don't think UDT in UDT is supported though.

baxslash
Valued Member
Bronze Codemaster
17
Years of Service
User Offline
Joined: 26th Dec 2006
Location: Duffield
Posted: 10th Oct 2013 08:16
I have used over 60. Not sure if there is an imposed limit on some platforms but that was tested on windows and iOS.

You ain't seen me right?
Ancient Lady
Valued Member
20
Years of Service
User Offline
Joined: 17th Mar 2004
Location: Anchorage, Alaska, USA
Posted: 10th Oct 2013 16:27
UDT in UDT is supported. Or at least it was. I used a lot of that when my WIP was being done in Tier 1.

You need to make sure that the UDTs are defined in the order they are used. If UDT B has an element that is UDT A, then UDT A must be defined first.

It is probably a good idea to be explicit about type in the UDT definitions and not just let it default to type based on the name of the element. That makes it a bit easier for the compiler to get the sizes of everything correct.

Cheers,
Ancient Lady
AGK Community Tester and AppGameKit Master
Auger
12
Years of Service
User Offline
Joined: 21st Aug 2011
Location: Out There
Posted: 10th Oct 2013 22:15
Whoops misread the question. Thought you meant parameters passed to a function.


Auger

Login to post a reply

Server time is: 2024-05-07 10:52:01
Your offset time is: 2024-05-07 10:52:01