[AC-924] Navigation windows delayed rendering
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Cannot Reproduce |
| Resolution Date | 2015-06-29T18:46:14.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Alloy |
| Labels | navigationWindow |
| Reporter | Samie Syed |
| Assignee | Radamantis Torres-Lechuga |
| Created | 2014-10-01T17:03:15.000+0000 |
| Updated | 2016-03-08T07:37:14.000+0000 |
Description
There is a delayed response in rendering the screen properly with sub navigation windows by 1 seconds.
So if I create a navigation window, and then open the child navigation window, it takes 1 second for the screen to completely render. I will see the old layout, then the new one shortly after wards.
I open them like this:
var controller = Alloy.createController('filters', {
title : 'Filter',
name : '_filters',
flagWin : true,
isFlyout : false
});
var newWindow = controller.getView();
Alloy.Globals.navGroup.openWindow(newWindow, {
animated : true
});
Window then opens, and it is glitchy. The user sees the old layout for 1 second, then it changes to the new layout.
In the simulator, the window opens smoothly with the view content in the position. I see it on my iPhone 4, so to replicate the bug you need to test it on a device.
Here is my XML:
Update:
$.win.addEventListener('open', function(e) {
//show content when window has opened.
$.winContent.visible = true;
});
This works, BUT it feels like a bit of a hack, given that I didn't have to wait for the window to open before showing the content properly.
David, I am glad to see that I am not the only one that is experiencing this. I am not sure how to fix it, and it is really annoying given that my app is slightly glitchy now. For example, the back buttons glitch up when you go to the next window - you see the old default nav group button glitch up for a second, than my new one which messes up the user experience. The way I resolved that was to use a 3rd party module to delete the old back button, and than replace it with news ones. It looks better, but again you will see the rendering flicker a bit and it is a bit of a hack!
Yes, I have no solution also. It's sad that such undesired bug had no comments from appcelerator's team so far
David, I suspect that is because they are not aware of it. I often find that a lot of these bugs appear on an actual device. I suspect that the guys at appcelerator do not properly test titanium on every hand held device, leaving us developers to be the guinea pigs. I am glad you replied, because it gives credibility to the problem.
[~davidbenko], [~maveick2k]: Guys, can you please provide info about: - In which device do you see this issues? - Do you have different testcases to the one here? Would be really nice if we have more info on this. If you have any sample code in Ti Classic, would be awesome. - Does this happen with simple windows on slow devices? Or you need to have a super complex window in order to be able to reproduce this? Thanks in advance!
Mauro, I have the same bug, but with simple (not navigation) window ( in fact, inside I have 3 children views ) The bug occurs on iOS (3.4.1GA), at simulator and device (5,6,6plus) however at (4S,5S) it works. My XML