-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[iOS] ScrollView inside a nested RadSideDrawer incorrect layout #7185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @erjdriver, |
You're saying no Then where would I put the My actual page is not the root/starting page of the page, it's just another page the user can navigate to - so there's a limit to how much I can change. I'd prefer to get this working as is considering...this same code works on Android and did on ios until about 2-3 months ago - so it's a bug in NS. But I'd be happy to change things as long as I can have the ActionBar and also be able to navigate to this page (i.e. not a root page). If I remove the ActionBar - the offset is less. This problem can be easily replicated by creating a sample tsc project and replace the main-page.xml with my code above. |
Hi @erjdriver, It will also help if you can send a project, which can be used for debugging. |
Here's the project with the problem. I just did Then added The latest NS versions are installed - 5.3.x The simulator is running iPhone 6 running ios 12.2. |
I followed your suggestion - and attached is the app with RadSideDrawer in app-root.xml file. In But if the Please see attached screenshot. The layout goes all the way to the top of the device screen (shown in blue. Looks like the parent GridLayout starts at y-offset 0 and again there's an offset before the child ScrollView is rendered (area shown in blue). Works fine on Android (top screenshot). Again, there seems to be a layout bug in the ios version - proven by both this and the earlier submitted versions. I would like the earlier project to work as is - as the second one would require quite a bit of changes in my code - and also I've got some pages without Thank you. |
I do have the same issue especially when I use RadListView or RadDataForm. |
@tsonevn - as requested I submitted a project with the issue - above with the attached layout-problem.zip file. Did you get a chance to replicate it? The last attached zip file above - the problem occurs if the In the the second to last attached zip file - is the original code that I'd like to get working (w/o moving the sidedrawer to the root). That problem occurs everytime and should be easy to replicate. Thanks. |
Hi @erjdriver, |
I don't understand how you can close this issue - it's a bug! Ok - you're saying for pages with You're saying for pages with OUT NS guys - too many times when I report a bug - it's not fixed. Usually the solution is a workaround or suggestions of code changes on my end. I'm working on a production software and there are limits to how much changes I can make without causing unforeseen issues. I appreciate the tool, doesn't matter if it's free or for purchase - bottom line is that - if you guys want this to be used in production app development - it has to be stable and reliable. |
Here's my code about the issue. just to precise I am not using ScrollView but I do get the same result (top space) also the issue is iOS only. Thanks. |
I've implemented my app with RadSideDrawer in the root file now. Unfortunately, the menu also appears on some pages where it shouldn't because of gestures - so I disabled gestures. Side-effect of this workaround. Please tag this issue as a bug. Thanks. |
@erjdriver as of this moment the RadSideDrawer (adn with latest versions) is supported only as a root. Here is how to prevent the drawer from being opened. |
This is a repeat of issue #6674.
Aplogies - but I posted at the end of that issue and getting no response.
The issue is: With the following xml, sometimes it creates an extra margin at the top - the green part of the image (ios only).
main-page.xml.txt
Using the latest environment 5.3.x
The text was updated successfully, but these errors were encountered: