Related
Hi,
I have an application which has been running nicely on Harrier and iMate devices, well any PPC devices really because of their rectangular screen shape.
My client has gone and bought some Palm Treo 700wx devices, and they have a smaller square screen.
In the resource of my project the screens are designed to fit PPC. When it runs on the Treo the Treo automatically pops up a scroll bar to allow the whole view to be seen.
The issue is when I first go into the app I can't see the top of the screen, about 20 odd pixels heigh aren't displayed. The scroll bar still displays and I can scroll down to the bottom of the view, and when I scroll up again the top of the screen is still out of sight.
If I exit the app just by tapping on the x in the top right corner (so the app is still running, not exiting properly via my Exit button which shuts down the app), I exit the app and then when I go back into the app the screens are displayed correctly, there is no missing space at the top of the screen.
If I exit the app via my exit button and then start the app again, the top of the view is missing again.
Does anyone know why the screen isn't displayed correctly when I first enter the app, or why it should come right when reloading the view again? Has anyone else had problems with screen layout when putting PPC apps on the square Treo 700wx?
Thanks
It sounds like you have a 'refresh' problem. I haven't encountered this my self and it is really hard to diagnose when you don't even tell us what language your app is written in, but basically here is what I think happens:
When your app is launched, part of its window doesn't get properly painted (not sure why exactly).
When you click the X the app isn't closed, but minimized.
When you return to it the window is maximized and repainted. Second repaint goes correctly.
The quick solution to this would be to force a window refresh just after the app is fully started.
Sorry I forgot to add the language.. it's written in eVC++ 3.0
I'll give the refresh a go, thanks
Further Questions..
I thought that minimising and then maximising the screen fixed the problem, but only partially..
Because the screen in resource is designed for regular PPC it is bigger than the Treo 700 screen size, so the OS automatically shows a scroll bar.
The new issue I'm seeing is to do with the scroll bar. The steps I take to reproduce the issue are:
1. Go to View1, and I scroll down the view (I'm using CView not CDialog)
2. Go to View2
3. Go back to View1. When I go back to the first view the scrollbar is scrolled down in the position I left it.
4. Scroll up to top of view and some of the controls in the wrong place. Some controls I dynamically create in OnInitialUpdate, and as part of the Create() I pass in CRect to tell it where to create the control.
If I set CRect.top to say 10, it's created 10 down from the top of the visible screen. The problem is that because I've scrolled the view previously the view draws it 10 down on the visible portion of the view.
I had thought that the easiest solution would be to always reset the scroll bar to the top of the view before creating my controls, but I'm not sure how to force the OS scroll bar to the top of the view. I've tried SetScrollPos(0,0) or ScrollWindow(0, y). ScrollWindow moves the actual view up or down, but the OS scrollbar is still in the same position.
Any ideas on how to set my view window to the top and to reset the scrollbar?
Thanks again
How to refresh a view?
I have sorted the issue mentioned just above, by finding the scroll position and factoring in that when I set the value of CRect area of the controls I need to dynamically draw.
I'm now just left with the first issue, of when I first start up the app the top part of the window and scrollbar are covered by the Title/Taskbar at the top of the screen.
If I close the app via the x button and restart the app, the issue resolves itself. Or if I open up any dlg like the About screen or even display an AfxMessageBox, when I close the dialog the original screen is redrawn correctly, in the correct position and scroll bar fully shown.
I have tried calling RecalcLayout(), RefreshWindow(), UpdateWindow(), Sending WM_SIZE messages and a whole range of things, but I can't seem to get the screen refreshing correctly apart from when I open any dialog and close that dialog.
When you close a dialog what messages get sent to the previous view that force it to redraw? Does anyone have any suggestions how I can force a refresh myself?
Thanks again
Did you try InvalidateRect?
I am getting a bit rusty with MFC, since I now try to do things the hard way and use pure win 32, but this should work.
If you can't use it as a class member, call the API directly using you view GetSafeHwnd() function for window handle). Use NULL for lpRect to redraw the whole window and FALSE for bErase to prevent flickering.
Note that UpdateWindow() only triggers repaint if part of the window becomes invalid (the contents needs redrawing).
No I hadn't thought of using InvalidateRect(), so I should give it a go.
In the end I just wanted the issue fixed so opted for a quick 'n dirty solution of displaying a temp CDialog as soon as the app starts and calling EndDialog() immediately in the OnInitDialog() so the dialog disappears before you see it.
It worked and the original screen gets updated to correct size, layout and scroll bar.
Cheers.
I've done a search in both the Leo forums as well as xda in general and can't see a solution for my problem:
I am unable to scroll within excel mobile. Whenever I drag my finger across the screen it selects cells rather than scrolling. This isn't a problem if I wish to move up and down as the vertical scroll bar is visible and can be used. However, the horizontal scroll bar doesn't display even though it is selected in the menu.
Can anyone suggest what I can do to fix this? Thanks in advance.
bump
can anyone help?
When you open Excel, click on the right side of the screen (= scroll bar) and the scroll-button will appear. Use that to scroll up and down. The same goes for the horizontal scroll bar (well, it's on the bottom of the Excel screen and you scroll from left to right ;-)). Should be there, otherwise I wouldn't know.
Thanks for the reply but unfortunately the horizontal scroll bar isn't visible on the screen, even though when I go into view -> show the horizontal scroll bar checkbox is ticked.
The vertical scroll bar also works like a "normal" scroll bar in that the scrolling part is always the same size; it doesn't increase in size when the scroll bar is tapped on. However, I seem to remember that's how it used to work when I first got the phone, so perhaps in all the various tweaks and things I've done since I've unwittingly edited something that is affecting it?!
Oh well.
You're not in full screen mode are you?
And have you tried opening a new document?
No not in full screen mode, and I have opened various different (existing) spreadsheets, and tried creating a new one and the same thing happens in all of them.
I've solved the problem. A little look into HD2Tweak and I spotted an option for horizontal scroll bar which was set to none. I changed it to normal and a quick soft reset later and I was able to see the horizontal scroll bar again; not just in Excel but other apps too.
I don't remember switching it to none, but am just glad it's working again now!
My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.
The softkeys are enabled within the framework.
Sent from my Nexus 4 using Tapatalk 4
Help
manojsap said:
My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.
Click to expand...
Click to collapse
same issue here even i try a factory reset
I flash the stock rom again and no clue of what to do
The exact same issue here, started behaving quirky since 4.3 and went bat**** crazy after the update second 4.3 ota (1.8mb patch google released recently). i used developer options to show the on screen touch blobs as well and it registers touches in the nav bar area, it just will not work in portriat (or rather that section of the screen) It is extremely frustrating.
I even went as far as to use adb and fastboot to restore my phone to stock 4.3 which would remove all files and place a stock 4.3 directly from dev.google but still It doesn't work.
The same issue
Im having this exact issue just a few days after i install a new update i hope that its a software issue :crying: and if is not warranty will cover it?
Navigation Bar issue
Same problem here , wont respond on portrait mode.
I did try to downgrade my android version to 4.2.2 (from 4.3) after the factory reset did not work, that did not work either.
Any ideas? could use some help
I have the same problem, I tried to restore the 4.3, the 4.2, but the problem remains, I also tried the cyanogenmod and 4.4, but it still does not work the navbar in portrait mode ..
No one knows a solution to the problem? You may have a hardware problem? Who takes care of the navbar?
Having the same issue here. Works in Landscape but not portrait. It went spastic this morning randomnly opening the clock and pullin the bar down itself. Show touches showed it registering touches all around the nav bar then suddenly it stopped. I cant use the bar now at all in portrait but the random touches are gone. I downloaded a touch detector and it shows all the way up to where the nav bar would be then deadzone, but fine in landscape again
anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...
sorschumi said:
anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...
Click to expand...
Click to collapse
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.
Same issue here
Tried lot of things still not working .........
pls someone find the solution.......
skycoresaunish said:
Tried lot of things still not working .........
pls someone find the solution.......
Click to expand...
Click to collapse
I think it's a hardware problem. Mine just went bad as well.
I have this problem now, too. Google now NAVRING still works to open Google Now from the middle nav button, which is why I do not understand why they nav bars do not work at seemingly the bottom of the screen. It just seems like that part of the screen has died, though some times it randomly works....... what the hell is this?
Huawei ascend mate navbar problem
I have same problem. And not only that my landscape control also got messed up After factory reset.
Also when I try to scroll down the web page in landscape mode it dosent work on the same area. So does this mean screen is screen is not registering my touch.
Some times the middle button start acting funny. It operates by itself even the internet is off. Like virus or some thing I did checked with antivirus nothing found. After activating show touch option it is shows Google shortcut is always pressed.
Dont know how to fix. Dont know the reason pls. Help. Xda.
Do you use dt2w? For me, after enabling that feature this would happen after a while. The borders of the screen would become unresponsive. I disabled dt2w, rebooted and it was fine again.
Sent from my Nexus 4 using XDA Free mobile app
Hi to everyone!
I have the same problem since some days with the nav bar on stock 4.4.2. Factory reset + rom flash via fastboot + CM 11 innstallation did not help at all. I'll bring my Nexus 4 today back to the retailer for reparation / replacing.
I'll inform you guys about the report of service center but it can take up to 45 days.
Thanks. This works for me
haris0032 said:
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.
Click to expand...
Click to collapse
Hi, I was facing the same issue on my mako. It just started without any notice. Being a flashaholic I thought it could be due to something I installed. Tried a lot of differnt ROMS including stock but no luck. Read somewhere about the "Show touch" function in the developer options and found that almost 7.5mm of the bottom of screen was not responding to touch. I then installed the stock 4.4.3 ROM, rooted it and installed gravity box. In Gravity I changed the navigation bar height to 120% and selected "keep at bottom" for landscape. I am now able to use the phone. I wish some custom ROMS start implementing 52dp height option so we could use these directly. I tried using gravity with Mahdi ROM but there is some conflict and I cant see the recents button. Also, the NB reverts to original and it needs to be enabled again manually
But thanks anyways. I dont want to buy a new phone for the next 6 months and this will work well for me.
Cheers
I made this mod for my GF, and share it here in case someone is interested.
It enables both floating multiwindows, and quad view KK style (up to 4 static windows on the same screen).
DISCLAIMER
I'm not responsible for anything that may happen, your Tab, your responsability
This mod has only be tested on the T111, but I'm pretty sure that it works as well on s110 and other 7 inches variants.
It may work on 8 in and 10 in variants, and in any case trying won't brick your phone so go for it!:silly:
If you do try please report here if it works.
It should work on both odexed and deodexed ROMs.
REQUIREMENTS
A Tab with a custom recovey.
INSTALLATION
Download the attached zip, flash it in recovery, reboot.
HOW TO USE THE MOD
Enable Multi Windows from your quick settings.
Floating:
Click on an app in the flash bar (the bar on the side from where Multi Windows are launched), the app will open in Floating Mode.
You will notice 3 buttons, minimize, maximize and close, and you can drag the window anywhere on the screen by dragging its upper left side.
You can resize it too, from the sides.
When an app has been minimized it becomes a small bar that you can drag anywhere, double tap it to maximize the window again.
Quad View:
Drag an app, if you put it in the center of the screen it will open in floating mode, if you put it at the top or the bottom of the screen it will open in full screen mode.
After one app is opened in full screen mode you can drag a second one to the second half on the screen, then a third to one corner and a fourth to the last corner.
The white central bar allows you to resize the windows in both length and width.
Don't touch the part where there's no bar between the windows cuz it makes the bar disappear (bug). If it happens just push home and reopen the windows.
SCREENSHOTS?
Nope, sorry, I have no time to play with that kind of stuff.
Try this mod if you feel like it, otherwise give it a miss, no worries...
UPDATES?
I have 2-3 things in my mind (windows templates, multiinstance) and I may implement them if I have time and if I see that enough people are interested.
Hello,
I am suffering from a really annoying problem for the last month and I cannot find a solution. I have tried to flash several firmwares but the EPD navigation bar seems to become somehow irresponsibe making the phone quite unusable.
With LP EU (5.0.0-EU1.1.87a and 5.0.0-EU1.1.124b) the navigation bar on the EPD seems to be working on the YotaHub without problems, I can navigate and I can unlock the screen by either double tapping or sliding. However, when I enable the YotaMirror the screen is mirrored but the Navigation bar becomes somehow disabled so I cannot exit the application that is running. The only way is turning on the normal screen so the EPD goes back to the YotaHub (quite annoying).
With LP RU (5.0.0-RU1.1.124 and 134 sideload) the YotaHub works fine but when I enable the YotaMirror a message saying "YotaMirror mode is enabled" with a help message explaining how it works and two buttons "Skip" and "Continue" which do not respond to any action; making it impossible to leave that screen. The only way to get rid of this is going to the normal screen and opening the YotaHub settings. This error seems to be already reported by another user: https://forum.xda-developers.com/yo...phone-201-stuck-androis-5-0-ru-1-124-t3571739
In MM (EU and RU) the area of the Navigation bar, no matter if YotaHub or YottaMirror seems irresponsible to any actions; so I cannot move across the panels in YotaHub nor exit an application opened in YotaMirror.
I thought this could be a hardware issue but I have discarded the option knowing that in LP it works and in both LP and MM the double tap unlocking feature (once enabled) unlocks the screen even being tap on that area.
I will continue flashing firmwares and eventually come back to the version of LP that was working fine (I cannot recall which one was it so I am downloading and trying most of them). But any help would be appreciated.
Thanks!
jaboto said:
Hello,
I am suffering from a really annoying problem for the last month and I cannot find a solution. I have tried to flash several firmwares but the EPD navigation bar seems to become somehow irresponsibe making the phone quite unusable.
With LP EU (5.0.0-EU1.1.87a and 5.0.0-EU1.1.124b) the navigation bar on the EPD seems to be working on the YotaHub without problems, I can navigate and I can unlock the screen by either double tapping or sliding. However, when I enable the YotaMirror the screen is mirrored but the Navigation bar becomes somehow disabled so I cannot exit the application that is running. The only way is turning on the normal screen so the EPD goes back to the YotaHub (quite annoying).
With LP RU (5.0.0-RU1.1.124 and 134 sideload) the YotaHub works fine but when I enable the YotaMirror a message saying "YotaMirror mode is enabled" with a help message explaining how it works and two buttons "Skip" and "Continue" which do not respond to any action; making it impossible to leave that screen. The only way to get rid of this is going to the normal screen and opening the YotaHub settings. This error seems to be already reported by another user: https://forum.xda-developers.com/yo...phone-201-stuck-androis-5-0-ru-1-124-t3571739
In MM (EU and RU) the area of the Navigation bar, no matter if YotaHub or YottaMirror seems irresponsible to any actions; so I cannot move across the panels in YotaHub nor exit an application opened in YotaMirror.
I thought this could be a hardware issue but I have discarded the option knowing that in LP it works and in both LP and MM the double tap unlocking feature (once enabled) unlocks the screen even being tap on that area.
I will continue flashing firmwares and eventually come back to the version of LP that was working fine (I cannot recall which one was it so I am downloading and trying most of them). But any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Can you unlock the back display without doubletap? So by using the power button when the epd display is facing up. IE, does it still correctly sense which display is facing up?
Hi @tomgaga Thanks for your response.
I can unlock the screen with in every mode: double tap, swipe and power.
I can fully confirm that this is not a hardware issue, meaning that the screen gets the touches as I have just captured the events with adb and saw how the screen gets the input event on the area of the screen "YotaMirror is enabled" that allows me to "Continue" or "Skip". So the taps are registered but it seems that this notification doesn't seems to work.
Anyone knows how to avoid this notification? I think this could solve the issue...
jaboto said:
Hi @tomgaga Thanks for your response.
I can unlock the screen with in every mode: double tap, swipe and power.
I can fully confirm that this is not a hardware issue, meaning that the screen gets the touches as I have just captured the events with adb and saw how the screen gets the input event on the area of the screen "YotaMirror is enabled" that allows me to "Continue" or "Skip". So the taps are registered but it seems that this notification doesn't seems to work.
Anyone knows how to avoid this notification? I think this could solve the issue...
Click to expand...
Click to collapse
I had this problem when using gravitybox from xposed and made an adjustment to the navigation bar. You got any mods installed?
@tomgaga , I didn't install xposed until now, I also tried to increase the size of the navbar with a mod but it seems to not doing the trick (I have the impression that the nav bar on the EPD doesn't get affected by this). When you had this issue did it go away by just removing the mod? Or you increased the size? However, I believe that after a full reset this should be gone...
Danke!
jaboto said:
@tomgaga , I didn't install xposed until now, I also tried to increase the size of the navbar with a mod but it seems to not doing the trick (I have the impression that the nav bar on the EPD doesn't get affected by this). When you had this issue did it go away by just removing the mod? Or you increased the size? However, I believe that after a full reset this should be gone...
Danke!
Click to expand...
Click to collapse
Yeah if you reinstalled the system images and reset the data, then any mod should be gone, but not if you just did a factory reset.
And the problem went away after I removed the mod yes.
tomgaga said:
Yeah if you reinstalled the system images and reset the data, then any mod should be gone, but not if you just did a factory reset.
And the problem went away after I removed the mod yes.
Click to expand...
Click to collapse
Hi again @tomgaga. The thing is that I reinstalled the ROM many times and I did full factory reset every time, so for me it seems there is an issue coming from somewhere else... Thanks anyway for your comments.