#1 is a normal and standard way in iOS, and I do not want to talk about it!
#2 is an unusual way but may be some of developers want to be use it, if you want work on this way i can add a property to this control for selecting pvStandard or pvStretch
However, both methods can be useful,
thanks your works
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, the property is a good idea, but I think it should have 4 values:
pvStandard162px, pvStandard180px, pvStandard216px and pvStretch, this way the user will see the standard sizes and he/she doesn't have to remember them. And if it set to a Standard size, we can resize the control and prevent the Height property from modifiing, otherwise we use the Height value.
What do you think, how much time it will take for you to make it? (Or should I do it?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's been a while since the last version, but the new one is here :) The NavController was a very hard control, because Apple uses some tricky rules to determine the appearance of it, so I have to figure them out. Because of it, I would like to ask everyone who uses it, to check it, and if find some rendering error please report it with a screenshot and a sample code. I tried to do my best to represent its original iOS appearance, but I haven't got enough time to do it pixel-accurate.
So the changelog (based on v3.0.0 + UINavigationController[r117]):
1. Supported control: NavigationController
2. Simplified Button's Paint method a bit.
3. Fixed NavigationController ToolBar Visible bug (see notes below).
4. Slider bug was fixed (see notes).
Notes:
Babak, in the NavigationController the FBarVisible and FToolbarVisible variables aren't needed, we can get these values directly from the underlying controls. So I added a GetBarVisible and GetToolBarVisible functions, because the object inspector shows that the ToolBar isn't visible, however it was. Now there is no need for the extra vars.
Also there is a message in the TDPFNavigationToolBar.Paint method (line #1474) for you, to change something, check it, thanks.
In the Slider, I made a patch for ticket #32, but when you implemented it, you forgot 4 lines. By the 3.0.0 if you set the MinimumValue to 50 and then the MaximumValue to 20 it causes a rendering error (Min = 50, Max = 20). So I've fixed this bug again, and also add more lines to the IOS code, because if the Value changed because of the Min or Max, it won't changed on the IOS.
Thanks for the good work of everyone!
Greetings!
PS.: If you got any errors in the IDE (like Access Violation) due to the NavContr. rendering, please report the bug and check Line #1599 in the DPF.iOS.UINavigationController.pas for temporary solution! Thanks.
As you can see in the Resources folder, I add the 'iOS6' tag to every PNG, so I thought about the future. But now I have absolutely no time for it, sorry, 'cause I'm working on the TableView, and if I completed all the visual controls, I should take care of my own app. But the steps are the followings:
1. Create every PNG in iOS7 look.
2. Check every control for rendering and sizing differencies and implement the Painting code according to this.
3. Implement a compiler directive to the DesignTime unit, so you can choose between iOS6 or 7 look before installing.
4. Make all the neccessary changes to the DesignTime unit based on that compiler directive.
On the other hand, I think we should wait for the final version of iOS7, to avoid the "double work".
Greetings
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What do you think, when the TableView will be finished? Because I started to work on it a few days ago, but it changes a lot, which is not bad, but what do you think, will it got some new designing stuff, or it can be considered as final now?
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Babak, I think I'm doing something wrong, but I can't see the MPVolume control in runtime. I put one onto the Form, run the app, but the Form is empty :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, Fenistil
#1 is a normal and standard way in iOS, and I do not want to talk about it!
#2 is an unusual way but may be some of developers want to be use it, if you want work on this way i can add a property to this control for selecting pvStandard or pvStretch
However, both methods can be useful,
thanks your works
Ok, the property is a good idea, but I think it should have 4 values:
pvStandard162px, pvStandard180px, pvStandard216px and pvStretch, this way the user will see the standard sizes and he/she doesn't have to remember them. And if it set to a Standard size, we can resize the control and prevent the Height property from modifiing, otherwise we use the Height value.
What do you think, how much time it will take for you to make it? (Or should I do it?)
I vote for this all-in-one solution (great work, btw)
Hi, Feni
I'll upload a new version tonight.
Regards
New version is here, based on v2.7.0.
Changelog:
1. New control supported: PickerView
2. Fixed Text Alignment in designtime
Babak: You've forgotten to include my last ZIP in the framework (which includes the TabControl), so I added it to this version.
Last edit: Fenistil 2013-08-08
Hi, Fenistil
I'm sorry,
I added last changes in new release
The Tabbar and ListPicker is a very nice and efficient.
very thanks to your good work
I'm glad to hear that and thanks for the new redesigned NavController, I'll work on it now.
Hi Fenistil
I added a toolbar to TDPFNavigationController.
I'll upload a new version of an hour after.
Thanks again to your good work.
Hi everyone!
It's been a while since the last version, but the new one is here :) The NavController was a very hard control, because Apple uses some tricky rules to determine the appearance of it, so I have to figure them out. Because of it, I would like to ask everyone who uses it, to check it, and if find some rendering error please report it with a screenshot and a sample code. I tried to do my best to represent its original iOS appearance, but I haven't got enough time to do it pixel-accurate.
So the changelog (based on v3.0.0 + UINavigationController[r117]):
1. Supported control: NavigationController
2. Simplified Button's Paint method a bit.
3. Fixed NavigationController ToolBar Visible bug (see notes below).
4. Slider bug was fixed (see notes).
Notes:
Babak, in the NavigationController the FBarVisible and FToolbarVisible variables aren't needed, we can get these values directly from the underlying controls. So I added a GetBarVisible and GetToolBarVisible functions, because the object inspector shows that the ToolBar isn't visible, however it was. Now there is no need for the extra vars.
Also there is a message in the TDPFNavigationToolBar.Paint method (line #1474) for you, to change something, check it, thanks.
In the Slider, I made a patch for ticket #32, but when you implemented it, you forgot 4 lines. By the 3.0.0 if you set the MinimumValue to 50 and then the MaximumValue to 20 it causes a rendering error (Min = 50, Max = 20). So I've fixed this bug again, and also add more lines to the IOS code, because if the Value changed because of the Min or Max, it won't changed on the IOS.
Thanks for the good work of everyone!
Greetings!
PS.: If you got any errors in the IDE (like Access Violation) due to the NavContr. rendering, please report the bug and check Line #1599 in the DPF.iOS.UINavigationController.pas for temporary solution! Thanks.
Related
Commit: [r117]
Last edit: Babak Yaghoobi 2013-08-20
Hi, Fenistil
I was very surprised to see Appearance. Thank you very much for your hard work.
It is truly amazing.
I sincerely thank you.
Will be added in the next release and the new version will be released today.
Kind Regards
Great work guys!
Do you think it is going to be hard to adapt de designtime components to acomplish the iOS7 look?
I'm a bit concerned about this... have any of you tried the componentes in iOS7 beta? Theoretically they should work...
Greetings
Hi!
As you can see in the Resources folder, I add the 'iOS6' tag to every PNG, so I thought about the future. But now I have absolutely no time for it, sorry, 'cause I'm working on the TableView, and if I completed all the visual controls, I should take care of my own app. But the steps are the followings:
1. Create every PNG in iOS7 look.
2. Check every control for rendering and sizing differencies and implement the Painting code according to this.
3. Implement a compiler directive to the DesignTime unit, so you can choose between iOS6 or 7 look before installing.
4. Make all the neccessary changes to the DesignTime unit based on that compiler directive.
On the other hand, I think we should wait for the final version of iOS7, to avoid the "double work".
Greetings
Hi, Fenistil
Thank you for your great work.
regards
Just asking....
I'm glad to hear that you are taking it into account!
Thanks for the info
Last edit: Diego 2013-08-21
Hi all!
While I'm working on the TableView I post a small improvement!
Changelog (based on v3.2.9):
1. Supported control: ActivityIndicator
Greetings
Thanks for the ActivityIndicator. I can´t wait to see the TableView in action!
Hi, Fenistil
Thank you your very good works,
I will, added next release,
Thank again
Regards
Hi all!
New version is here!
Changelog (based on v3.5.1):
1. New control supported: PageControl
Greetings!
Last edit: Fenistil 2013-08-25
Hi Fenistil
Thank you for your good work,
updated [code] section.
regards
Related
Code: code
Hi Babak!
What do you think, when the TableView will be finished? Because I started to work on it a few days ago, but it changes a lot, which is not bad, but what do you think, will it got some new designing stuff, or it can be considered as final now?
Thanks
Hi, Fenistil
I think the tableview is almost stable, and no need to be many changes,
Another two components: MPVolume and SearchBar also are waiting for you. :)
regards
Thanks, I go for it :)
Babak, I think I'm doing something wrong, but I can't see the MPVolume control in runtime. I put one onto the Form, run the app, but the Form is empty :(
Hi Fenistil
You can see MPVolum only in the Device, not show in the Simulator
Regards
Thanks!