121
NGUI 3 Support / Re: Having trouble with toggles
« on: April 06, 2014, 08:00:59 AM »
It's not exposed in the inspector for UIToggle.
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.
122
NGUI 3 Support / Ordering items in a horizontal scrollview.
« on: April 06, 2014, 07:56:20 AM »
I've got the following:
ScrollView
Grid (sorting horizontal)
item1
item2
item3
Items are being added to the Grid dynamically.
In the scrollview, the items are being randomly displayed. How to keep the ordering ?
ScrollView
Grid (sorting horizontal)
item1
item2
item3
Items are being added to the Grid dynamically.
In the scrollview, the items are being randomly displayed. How to keep the ordering ?
123
NGUI 3 Support / Re: Having trouble with toggles
« on: April 05, 2014, 12:15:37 PM »
Ok here's another attempt at describing the situation:
1. a horizontal scrollList with 5 photos.
2. each item is a clickable photo.
3. Initial state is no photos are selected/highlighted.
4. User clicks on the 1st photo. This then gets highlighted.
5. User clicks on 2nd photo, the 1st photo is un-highlighted and the 2nd is highlighted.
6. User clicks on 2nd photo again and now it also gets un-highlighted.
1. a horizontal scrollList with 5 photos.
2. each item is a clickable photo.
3. Initial state is no photos are selected/highlighted.
4. User clicks on the 1st photo. This then gets highlighted.
5. User clicks on 2nd photo, the 1st photo is un-highlighted and the 2nd is highlighted.
6. User clicks on 2nd photo again and now it also gets un-highlighted.
124
NGUI 3 Support / Re: Scrollview SelectedItem property ?
« on: April 05, 2014, 12:10:03 PM »
This is a bit too general.
I would like for the scrollview to know which of it's own items are being selected. Take for example, a list, if an item from a list is selected, then the list knows which item. So when an item of a scrollview gets selected, it should also know. Perhaps what I am refering to is a ScrollList component which is different from a more general scrollView - which is a more like a scrollable panel.
Perhaps there should be a new component called ScrollList / scrollGrid to differentiate between the more general scrollView-er.
I would like for the scrollview to know which of it's own items are being selected. Take for example, a list, if an item from a list is selected, then the list knows which item. So when an item of a scrollview gets selected, it should also know. Perhaps what I am refering to is a ScrollList component which is different from a more general scrollView - which is a more like a scrollable panel.
Perhaps there should be a new component called ScrollList / scrollGrid to differentiate between the more general scrollView-er.
125
NGUI 3 Support / Scrollview SelectedItem property ?
« on: April 05, 2014, 06:29:41 AM »
I have a Scrollview photo gallery.
1. When user clicks on a photo, the photo is highlighted.
2. Is there a SelectedItem property of the Scrollview that lets me know which photo item was selected ?
1. When user clicks on a photo, the photo is highlighted.
2. Is there a SelectedItem property of the Scrollview that lets me know which photo item was selected ?
126
NGUI 3 Support / Re: Having trouble with toggles
« on: April 05, 2014, 05:59:05 AM »
Hello, is there an answer to this ?
127
NGUI 3 Support / Re: Comparision of NGUI over new uGUI
« on: April 04, 2014, 06:03:46 AM »
Great idea that it should be on the asset store. They owe it to unity users. We've had to bear their mistakes in development for the past few years. Unity game devs are extremely forgiving as compared to business users. If Xamarin told its users that they have to wait for something for 2 years, it would have been a very different reaction. As for the core stuff, that included in the downloaded install. The uGUI code can be updated more frequently in this way. Also like UMA or LUX the community could also contribute to making it better.
128
Misc Archive / Re: Our game, with extensive NGUI UI, now available on all mobile platforms
« on: April 04, 2014, 05:53:06 AM »
Thanks for the great write up on your experience with NGUI. Very helpful tips.
1. Definitely agree with an improved workflow that allows designers and engineers to work independently. Later versions of Flex enabled this type of separation of concerns.
2. DataProvider. Good to know that you've also have Flex experience. I agree that the data binding in Flex is a bit of a black box and often times, we did have performance problems with their system. In regards to NGUI, I'm not proposing a Flex data-binding situation, I was referring for components to be able to be "Data Aware". Take for example a horizontal scrollList, currently, there is a UGrid that we can attach that will nicely layout the items into a grid structure. The data provider is another component or widget that we can attach to the scrollList that takes in a Json, array, List, etc. The scrollList then populates itself with the contents of the data. Very much like Flex but much more lightweight and as a component that we can customize using the inspector editor. With the upcoming building blocks of databinding and parameterized delegates, this could be the next step.
What I am thinking of is being able to more easily assemble new GUI components from prefabs, tack on a custom provider component, customize it, then feed in the data. This kind of workflow will make NGUI much more powerful. ATM, it's a lot of very tedious work to individually hook up each individual UISprite or widget.
As an example, if one were to build a data-aware scrollList like a photo gallery. How much work will it take ? The flex or old unity gui data driven approach is quite different. Start with a scrollList base, re-skin and add custom layout code or handler code for customization. Feed in the data and done.
1. Definitely agree with an improved workflow that allows designers and engineers to work independently. Later versions of Flex enabled this type of separation of concerns.
2. DataProvider. Good to know that you've also have Flex experience. I agree that the data binding in Flex is a bit of a black box and often times, we did have performance problems with their system. In regards to NGUI, I'm not proposing a Flex data-binding situation, I was referring for components to be able to be "Data Aware". Take for example a horizontal scrollList, currently, there is a UGrid that we can attach that will nicely layout the items into a grid structure. The data provider is another component or widget that we can attach to the scrollList that takes in a Json, array, List, etc. The scrollList then populates itself with the contents of the data. Very much like Flex but much more lightweight and as a component that we can customize using the inspector editor. With the upcoming building blocks of databinding and parameterized delegates, this could be the next step.
What I am thinking of is being able to more easily assemble new GUI components from prefabs, tack on a custom provider component, customize it, then feed in the data. This kind of workflow will make NGUI much more powerful. ATM, it's a lot of very tedious work to individually hook up each individual UISprite or widget.
As an example, if one were to build a data-aware scrollList like a photo gallery. How much work will it take ? The flex or old unity gui data driven approach is quite different. Start with a scrollList base, re-skin and add custom layout code or handler code for customization. Feed in the data and done.
129
NGUI 3 Support / Re: Comparision of NGUI over new uGUI
« on: April 03, 2014, 03:49:28 AM »
Definitely agree that support at NGUI has been superb. Nothing less than stellar.
Unity is a bit of a dead duck when it comes to fixing bugs. This has a very big impact on potential buyers for sure.
One thing that was mentioned by unity is that the source for uGUI will be available for tweaking. If this is the case, then probably there might be a mechanism for them to update the package more frequently via other channels rather than downloading the entire Unity install. However, given their track record, making frequent updates is not very likely.
So it seems that if NGUI's and the new uGUI is very much the same then NGUI is the clear winner.
Unity is a bit of a dead duck when it comes to fixing bugs. This has a very big impact on potential buyers for sure.
One thing that was mentioned by unity is that the source for uGUI will be available for tweaking. If this is the case, then probably there might be a mechanism for them to update the package more frequently via other channels rather than downloading the entire Unity install. However, given their track record, making frequent updates is not very likely.
So it seems that if NGUI's and the new uGUI is very much the same then NGUI is the clear winner.
130
NGUI 3 Support / Re: Having trouble with toggles
« on: April 02, 2014, 12:13:07 AM »
I have the same question.
On IOS,
The idea is tap item to Select, tap on the same item again to deselect.
On IOS,
The idea is tap item to Select, tap on the same item again to deselect.
131
NGUI 3 Support / Comparision of NGUI over new uGUI
« on: April 02, 2014, 12:03:26 AM »
Hi everyone,
I would like to start a discussion about something that's probably on everyone's mind at the moment. NGUI and new uGUI. Seems to me that both are very similar, so what is the advantage of using NGUI over uGUI ? I already own NGUI but to for new users, what is the reason to pay $95 for NGUI when uGUI is Free. I am playing devil's advocate to get ideas of the compelling difference between the two. Please feel free to contribute to this discussion.
I would like to start a discussion about something that's probably on everyone's mind at the moment. NGUI and new uGUI. Seems to me that both are very similar, so what is the advantage of using NGUI over uGUI ? I already own NGUI but to for new users, what is the reason to pay $95 for NGUI when uGUI is Free. I am playing devil's advocate to get ideas of the compelling difference between the two. Please feel free to contribute to this discussion.
132
Misc Archive / Re: Our game, with extensive NGUI UI, now available on all mobile platforms
« on: April 01, 2014, 11:56:18 PM »
Thanks for posting the game,
Would love to get some feedback on the following:
1. Pain points with NGUI
2. What and how it could be improved.
3. Would having components that have DataProvider functionality help. Ex: Feed in an xml or json to a scrollList comp and it auto populates. Something like Adobe Flex but without the bulk. Just a dataProvider and more developed component architecture.
Would love to get some feedback on the following:
1. Pain points with NGUI
2. What and how it could be improved.
3. Would having components that have DataProvider functionality help. Ex: Feed in an xml or json to a scrollList comp and it auto populates. Something like Adobe Flex but without the bulk. Just a dataProvider and more developed component architecture.
133
NGUI 3 Support / Re: I2 Localization for NGUI
« on: April 01, 2014, 07:46:24 AM »
Cool, I'll check out your plugin.
Also, my the main reason I'm asking about uGUI is that the old Unity GUI was very much data driven whereas NGUI is more graphic based. Wondering is uGUI will be more a mix between the old Data driven architecture and NGUI graphic approach.
Also, my the main reason I'm asking about uGUI is that the old Unity GUI was very much data driven whereas NGUI is more graphic based. Wondering is uGUI will be more a mix between the old Data driven architecture and NGUI graphic approach.
134
NGUI 3 Support / Re: Is it possible to support handlers that take arguments, in EventDelegate?
« on: March 30, 2014, 02:36:19 PM »
Awesome, NGUI is definitely getting better. Can't wait to try it.
135
NGUI 3 Support / Re: Dynamically adding items to scrollview via code. How to update scrollview.
« on: March 30, 2014, 02:30:49 PM »
"UIWidget.MarkParentAsChanged() must be called if you moved the widget from A to B."
You mean when one of the items of ScrollList A is moved to ScrollList B?
You mean when one of the items of ScrollList A is moved to ScrollList B?