Hello Guest

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - 1dayitwillmake

Pages: [1]
1
Support / Re: Extra tiny feature request
« on: May 31, 2014, 09:57:23 pm »
I could see your concern, in this case that value is only ever read and set internally. All existing uses of this this class, aren't even reading that value in any case.

However I still see your concern, just because from reading the forums it seems like that is always the constant fear that a new change will break something which I can totally understand. So I will simply 'extend' the class and add a 'SetDirty' method that simply flips that boolean.

Maybe set the parameter to protected as a compromise, keeping it basically private?

2
Support / Extra tiny feature request
« on: May 31, 2014, 08:23:10 pm »
I have a tiny feature request, which from what I can tell and tested should really not cause any issues.

In tk2dUIProgressBar could the paremter 'initializedSlicedSpriteDimensions' be made public?
A use case for this, is you have a progress bar which will be resized (or even sized once during set up), and you'd like to basically mark it as dirty so the 'fullSlicedSpriteDimensions' are recalculated.

Since that's all it really does, it doesn't seem like it'd have any side effects - what do you say?

3
Support / Re: Updating collider when re-positioning a button
« on: May 31, 2014, 07:35:25 pm »
Yeah, I noticed that - very strange because the objects are not marked as static.
I didn't see anything special in the UIDemo from which mine is based, in fact my buttons are just a modified version of the BasicButton (from Layout) prefab.


4
Support / Updating collider when re-positioning a button
« on: May 31, 2014, 07:12:38 pm »
I'm laying out some objects in code, however when I do that it seems that the colliders maintain their original position.

Previously I was just modifying the transform.localPosition, but I noticed that left the bounds incorrectly displayed in the editor.
So I switched to a simple wrapper that would take a Vec3 position and call SetBounds, but the collider is still in the incorrect spot.

What is the correct way to modify the dimensions / position of a UILayoutItem such that its collider is correctly updated?

Here's an image for reference

Pages: [1]