[SUGGESTION] Please remove or up the GUIControl limit to 50

Started by subspark, Mon 08/02/2010 07:39:47

Previous topic - Next topic

subspark

As the title suggests. :) We're making an awesome dynamic save/load system and like many others, we have reached the limit of 30.

Increasing this limit to 50 would solve our issue however I don't really know why there still is a limit on GUI controls. They certainly must be less expensive than the infinite amount of GUIs that can be created.

Cheers,
Sparky.

Khris


RickJ

I support the idea of increasing the limit.

There is some advantage to Khris's suggestion.   If you logically divide up your controls into groups and then put each control on a separate GUI you may find that it is much easier to manage the layout.  For example if you want to move a row of buttons it's very easy if they are on a separate GUI, you just move the GUI.

A more interesting suggestion is to add the ability to add a GUI within a GUI.  How is that different than what we can do now?

1.  Child GUI positions would be relaticve to the parent GUI's position. 

2.  Child properties such as visibility, enabled, etc would be overridden by changes to the parent's corresponding properties.  For example if the parent visible property is set to false parent and children GUIs are not longer visible.  If the parent 's visible property is true then then child GUIs are visible if their visible property is also true.

3.  GUI event handlers.  The child event handlers could be the same as the parent's by default.  In this way controls on child GUIs would be handled the same way as if they were on the parent GUI.

4. Import./Export - Export of  the parent GUI would also include the children by default.  There could be an option to the exclude children if necessary.  Import of the same would include whatever was exported.

Shane 'ProgZmax' Stevens

As a fan of dynamic sizes I'd rather the limit was user defined rather than some arbitrary amount that requires re-adjustment every year or so to accommodate authors with higher requirements.  As always, this becomes an issue of 'quick fix' vs a redesign that will ultimately make 'quick fixes' unnecessary, so I'm definitely in favor of limit removal for any/all content the engine allows.

Knox

Sorry if I replying in an old thread but I would also REALLY like the limits removed completly for gui controls...

In the meantime I can use multiple gui's buts its a pain in the azz!
--All that is necessary for evil to triumph is for good men to do nothing.

monkey0506

Knox, are you still using those GUI.Show and GUI.Hide functions I wrote for you? If so, you could just add exceptions for those GUIs which have controls delegated to other actual GUIs.

Code: ags
if (theGUI == gInventory) {
  gInvWindow.Show();
  gInvButtons.Show();
}


Or the like.

Knox

Hey Monkey!

Oh yeah I still use those...just would be nice to be able to use as many controls you want on gui's without resorting to work-arounds!
--All that is necessary for evil to triumph is for good men to do nothing.

monkey0506

Heh..sorry for not explicitly stating "yes, implementation is nice, but for your personal circumstances Knox, you could use.." :P

SMF spam blocked by CleanTalk