It's been a while since the last update, but it is here now :) Based on v2.2.1.
Changelog:
1. New control supported: Toolbar
Babak:
I've changed the Paint method of the UIButton, don't forget to update it, and please keep my original source format for the DesignTime.pas, because it is screwed up again in 2.2.1.
Babak, I'm working on the Navigation Controller, and either I don't understand exactly the usage of that control, or it should be implemented a little different way.
For my idea, check the attachment.
Because now if I change the PagePrompt of one of the BarItems, should I change all the other's for that UIView?
The navigation control is a little complex control,
you can set page prompt for any pageviews, but at design time all pageviews not visible then so all buttons !
this is better you wait to me for changing this control design time visibility like TabBar, then you can add your design time features.
thanks your good work
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I see, but I thought, you should change the class hiearcy to represent the PageViews as a TList and in every PageViews[].Item there must be a BarItems List, that contains the buttons for that PageView only. If you set the RootView of a PageView to true, the class should set the others' RootView to false, and call Invalidate (in designtime) to redraw the control with an another page displayed.
If I understand the working of that control, there must be only one RootView at a time, and the PagePrompt should be the same for all BarItems that belong to the same Page. So it's a bit confusing for a developer, because the PagePrompt can be set to more different values for the same Page (which one will display on iOS?), and there can be more RootView set to true at the same time.
Now I'll wait for it to be complete, meanwhile I go for the Page/Tab Controls.
Keep up the great work, greetings!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Changelog:
1. New control supported: TabBarController
Babak: I've made a lot of modification to the source of the TabBarController to make it works in the IDE as it would be on iOS. Please compare carefully the units and move all the new codes to the final version.
Now I'm working on the PickerView and this control should be 162, 180 or 216 pixel height (by Apple). In any other size it shows visual glitches on iOS. It works, but looks bad. So nobody should use any other height for that. So how should I implement it?
version (I prefer this way):
Modify the Resize function to allow only the above heights.
Draw the control visually perfect with 3 different bitmap series.
version:
Allow any height.
Use only one image for the drawing, and stretch it. This way even an 162px control would have glitches due to the resized images, but of course, only in the IDE.
Please reply or vote :)
Last edit: Fenistil 2013-08-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ohh, sorry
i will be add this property
thank you Fenistil
Ohh, sorry
i will be add it,
thanks
New version is here, based on v1.9.4.
Changelog:
1. New control supported: TextField
2. Added 4 PickerModes to DatePicker (Time, Date, DateAndTime, CountDown).
Greetings
Hi, Fenistil
Thank you,
Applied in 1.9.5
Great work Fenistil! Your effort is appreciated
Thanks :)
New version is here, based on 2.0.1.
Changelog
1. New control supported: Label, TextView
I'm currently working on the Toolbar, but it's a bit complex, it'll take a day or two to complete.
Greetings
Hi, Fenistil
Thank you for the good work,
Hi all!
It's been a while since the last update, but it is here now :) Based on v2.2.1.
Changelog:
1. New control supported: Toolbar
Babak:
I've changed the Paint method of the UIButton, don't forget to update it, and please keep my original source format for the DesignTime.pas, because it is screwed up again in 2.2.1.
Thanks, greetings!
Hi, Fenistil
thank you, for your good good work,
The toolbar is very beautiful!
Button & Toolbar applied to last source,
Thanks again
Nice to hear we already have the toolbar! Great work Fenistil.
I think most of the work you have done with the toolbar will also be useful for the UINavigationController (Their aspect is quite similar)
Thanks :)
I know the navigation controller and the toolbar can share a lot of code, so I'll do it next.
Babak, I'm working on the Navigation Controller, and either I don't understand exactly the usage of that control, or it should be implemented a little different way.
For my idea, check the attachment.
Because now if I change the PagePrompt of one of the BarItems, should I change all the other's for that UIView?
Last edit: Fenistil 2013-07-29
Hi, Fenistil
Thank you for you hard work,
The navigation control is a little complex control,
you can set page prompt for any pageviews, but at design time all pageviews not visible then so all buttons !
this is better you wait to me for changing this control design time visibility like TabBar, then you can add your design time features.
thanks your good work
Ok, I see, but I thought, you should change the class hiearcy to represent the PageViews as a TList and in every PageViews[].Item there must be a BarItems List, that contains the buttons for that PageView only. If you set the RootView of a PageView to true, the class should set the others' RootView to false, and call Invalidate (in designtime) to redraw the control with an another page displayed.
If I understand the working of that control, there must be only one RootView at a time, and the PagePrompt should be the same for all BarItems that belong to the same Page. So it's a bit confusing for a developer, because the PagePrompt can be set to more different values for the same Page (which one will display on iOS?), and there can be more RootView set to true at the same time.
Now I'll wait for it to be complete, meanwhile I go for the Page/Tab Controls.
Keep up the great work, greetings!
Hi, Fenistil
I will work on the redesign navigation but it's take me a lot of time,
thanks your good work
New version is here! Based on v2.2.1.
Changelog:
1. New controls supported: MapView, ProgressView
2. Added Toolbar's CustomView and ImageView support
Greetings :)
Hi, Fenistil
Thank you for new features
DPF.iOS.DesignTime.pas is old version and MapView not defined inside it,
please place last version.
Thanks
Sorry, attached the latest version.
Bug fix: Won't compile for iOS.
New version is here! Based on v2.6.0.
Changelog:
1. New control supported: TabBarController
Babak: I've made a lot of modification to the source of the TabBarController to make it works in the IDE as it would be on iOS. Please compare carefully the units and move all the new codes to the final version.
Thanks
Last edit: Fenistil 2013-08-06
Fenistil,
Great work!! Can't wait to see the next update!
Your efforts are much appreciated!
Thanks :)
Now I'm working on the PickerView and this control should be 162, 180 or 216 pixel height (by Apple). In any other size it shows visual glitches on iOS. It works, but looks bad. So nobody should use any other height for that. So how should I implement it?
version (I prefer this way):
Modify the Resize function to allow only the above heights.
Draw the control visually perfect with 3 different bitmap series.
version:
Allow any height.
Use only one image for the drawing, and stretch it. This way even an 162px control would have glitches due to the resized images, but of course, only in the IDE.
Please reply or vote :)
Last edit: Fenistil 2013-08-06
I think #1. I personally want it to represent what it will look like on the device.