4 Answers, 1 is accepted
0
Hi Alex,
Thank you very much for contacting us and for reporting this issue.
Indeed, the problem is present easily reproducible. We will need some more time to research it as this bug is tricky and there is no obvious explanation for it.
I have updated your Telerik points for your time and for bringing our attention to this issue. I will contact you back when we isolate the problem.
Kind regards,
Georgi
the Telerik team
Thank you very much for contacting us and for reporting this issue.
Indeed, the problem is present easily reproducible. We will need some more time to research it as this bug is tricky and there is no obvious explanation for it.
I have updated your Telerik points for your time and for bringing our attention to this issue. I will contact you back when we isolate the problem.
Kind regards,
Georgi
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
Hi Alex,
A quick update on the problem - I found the cause for this issue. When the application bar has opacity it is actually an overlay of the root frame and not part of the actual layout. This breaks our RadWindow's layout logic (RadWindow is used for the popup part of the picker).
I have fixed the bug and the fix will be available for the official Q3 2011 release - due in about two weeks.
Once again - thank you for your feedback, it really helps us build better tools.
All the best,
Georgi
the Telerik team
A quick update on the problem - I found the cause for this issue. When the application bar has opacity it is actually an overlay of the root frame and not part of the actual layout. This breaks our RadWindow's layout logic (RadWindow is used for the popup part of the picker).
I have fixed the bug and the fix will be available for the official Q3 2011 release - due in about two weeks.
Once again - thank you for your feedback, it really helps us build better tools.
All the best,
Georgi
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
Girish
Top achievements
Rank 1
Rank 1
answered on 28 May 2012, 02:42 PM
I am using the latest version of the RadListPicker (2012.1.321.2040), but the issue with transparent appbar still exists. The last item in the list is not selectable. Can you please suggest a solution or a workaround for this?
0
Lancelot
Top achievements
Rank 1
Rank 1
answered on 30 May 2012, 07:03 PM
Hi Girish,
I have encountered this problem in many of my apps. The workaround it to set the bottom margin of the control at least 72 pixels from the bottom of the root frame. This moves the "touchable area" above the transparent appBar.
Like Georgi says, when the appBar's transparency is set to 0.9 or below, the root frame expands to the bottom of the screen and the appbar shows over it. If any elements on screen get moved underneath the appBar (which is 72 pixels high) they become untouchable because the appBar is visually on top.
This has nothing to do with the RadControls themselves. If you were to place a regular wp7Button at the bottom, it would not be clickable either =/ There is no way to move an element in the visual tree higher than the appBar (this was done to maintain a consistent UI throughout the phone). So the only workaround is to prevent the listpicker from going into the unreachable 72 pixel area.
However, you can place everything into a ScrollViewer. Create a scrollviewer and place your UI into it and expand the bottom of your content grid 80 pixels below the Bottom of the appBar (essentially your content can go 80 pixels off the bottom of screen this lets the top of the screen scroll up 80px). This will let the user scroll down on your page and use the ListPicker properly.
I hope this explains things for you and let me know if there is anything I can do to help. If you provide the code for that particular page, I can help you directly.
Good Luck!
Lancelot
I have encountered this problem in many of my apps. The workaround it to set the bottom margin of the control at least 72 pixels from the bottom of the root frame. This moves the "touchable area" above the transparent appBar.
Like Georgi says, when the appBar's transparency is set to 0.9 or below, the root frame expands to the bottom of the screen and the appbar shows over it. If any elements on screen get moved underneath the appBar (which is 72 pixels high) they become untouchable because the appBar is visually on top.
This has nothing to do with the RadControls themselves. If you were to place a regular wp7Button at the bottom, it would not be clickable either =/ There is no way to move an element in the visual tree higher than the appBar (this was done to maintain a consistent UI throughout the phone). So the only workaround is to prevent the listpicker from going into the unreachable 72 pixel area.
However, you can place everything into a ScrollViewer. Create a scrollviewer and place your UI into it and expand the bottom of your content grid 80 pixels below the Bottom of the appBar (essentially your content can go 80 pixels off the bottom of screen this lets the top of the screen scroll up 80px). This will let the user scroll down on your page and use the ListPicker properly.
I hope this explains things for you and let me know if there is anything I can do to help. If you provide the code for that particular page, I can help you directly.
Good Luck!
Lancelot