Don't add DPFKeyboard or any other invisible components on the frames that used in the cells,
Add DPFKeyboard on the main form, only one instance of keyboard is enough for all forms in application.
Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have one main form, with a navcontroller on it..
everything else is just frame files..
I removed all copies of my keyboard.. and just have ONE component on my main form..but the behaviors dont seem to trickle down the the other views..
It seems like I need one per each view.. This is how I got into this mess in the first .. It seems ok, as long as I keep it off of my dynamic stuff.. Dynamic frame etc..
Am I right?
Last edit: Gordon 2014-01-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, you don't need one per each view, only on keyboard for all application is enough,
I do not recommend dynamic frames,
I don't know exactly what is the problem, may be you can send me a sample project.
Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I figured it out.. Im still a little confused on properties and what they all do..
There was a picker property that I wasnt using.. that combined with the fact that the simulator behaves much different than a real phone.. So. I think its ok..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My app was working perfectly.. Now all of a sudden, i have this strange error.. I dont think i changed any code.. so im really baffled..
It gives a type cast error.. on this code..
UIView( ( CustomFrame.Components[i] as TDPFiOSBaseControl ).UIControl ).setTag( TAG_BASE + i );
On line 2254 in DPF.iOS.UITableView
Did anything possibly change in this code? maybe its me,but I dont think I changed anything..
Any ideas?
Hi Gordon
1) May be one of your frame not created,
2) May be you are using a non DPF component in your frame! (one of FMX controls)
if you send me a sample project, I can see and find your problem.
Regards
Ok, I found the problem..
On the frame, I added a keyboard component.. because I wanted to control the 'Done" etc..
When you remove the keyboard component.. problem gone.. put it back, dies..
Not sure if its a bug? Im thinking so.. Ive attached code..
Hi Gordon,
Don't add DPFKeyboard or any other invisible components on the frames that used in the cells,
Add DPFKeyboard on the main form, only one instance of keyboard is enough for all forms in application.
Regards
Got it, thanks.. all is well now..
I have one main form, with a navcontroller on it..
everything else is just frame files..
I removed all copies of my keyboard.. and just have ONE component on my main form..but the behaviors dont seem to trickle down the the other views..
It seems like I need one per each view.. This is how I got into this mess in the first .. It seems ok, as long as I keep it off of my dynamic stuff.. Dynamic frame etc..
Am I right?
Last edit: Gordon 2014-01-21
Hi Gordon
No, you don't need one per each view, only on keyboard for all application is enough,
I do not recommend dynamic frames,
I don't know exactly what is the problem, may be you can send me a sample project.
Regards
I think I figured it out.. Im still a little confused on properties and what they all do..
There was a picker property that I wasnt using.. that combined with the fact that the simulator behaves much different than a real phone.. So. I think its ok..
Hi Gordon,
Can you tell me what exactly is the problem, please ?
Regards