Hi.
I am experiencing a strange problem, often the TP2 does not sense the "end of touch" when I lift my finger from the display... giving strange problems.
This happens both in Touch3D and other programs (like notes)
I suspect that some program might have changed the sensitivity setting.
please tell me that your default, original registry value is for
HKLM\Drivers\TouchPanel\PressureThreshold - mine is 18866
Thanks
AlCapone said:
please tell me that your default, original registry value is for
HKLM\Drivers\TouchPanel\PressureThreshold - mine is 18866
Thanks
Click to expand...
Click to collapse
mine is 61.
Funny mine is 2710, stock 1.19_PTG rom, working great though.
mine says 59
Mine is 10000
+1 Mine is 10000
Mine is 10,000 too -
10,000 on mine as well..
I had set 200.
Changed on 10000 and fell differend. Its much better now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I do have Touchresponse set to maximum...
Related
Just on the off chance...
Would any person know of a good class for handling BeginWaitCursor / EndWaitCursor. Which is:
- External to any one form.
- Holds a count of calls, so that cancels at correct place.
- Can be interupted, say to display a message, then shown as before.
- Works with a multi-thread application.
- If possible, locks user input when active. (like a model wait cursor)
- (etc)
Ben.
You may want to ask CharlyV in this forum - specifically this thread..
http://discussion.brighthand.com/showthread.php?s=&threadid=97029
We've been creating neat little system wait icons in there...
-JB
Like the idea of changing the wait cursor. (The word 'wait' seems slightly superfluous, since it's the only cursor...) Nice site, I look forward to seeing what response I get.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ben
I've been searching on XDA and Google but I couldn't find anything about this. I also don't know if this is a common bug or whatever. I was just fiddling with my phone when I saw at the Hardware information page that I had 768mb ram (Geheugen in Dutch) instead of the normal 512mb. Is this just a display bug?
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry in advance if this has been asked already, I just couldn't find anything about it and was curious.
I believe its just a display bug, mine once show 768 too, but I recently (like 10 minutes ago) change ROM and I just checked and it says 512 again. Or maybe is because of where the ROMS are taken to make our costume ROMs. Now I'm curious too.
Great to see someone finally reacting to this! Yeh, I'm still awaiting an answer to this, though I think it is indeed just a display bug. Currently without my G2 though due to repairs.
Hey guys, i was making an apk with my skin and the layout get messed.
Tested in a smartphone with bigger resolution, is it normal?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry my english
error404 said:
Hey guys, i was making an apk with my skin and the layout get messed.
Tested in a smartphone with bigger resolution, is it normal?
Sorry my english
Click to expand...
Click to collapse
My guess from looking at the pictures is that you choose a different anchorpoint for the module that renders the menu icon. Probably center left while the rest is on center? If you want elements to stay together if the widget get resized you should use the same anchorpoint for all modules so something like this doesn't happen
I think the problem is the device resolution, because i created this in a 480x800 and i'm testing in a 1080x1920. Tried what you said and the problem continues.
I've seen some pretty advance graphing in widget. Wondering how these were made, whether with very advanced mathematical statements and Zooper code, or some other way.
I understand how the line graph could possibly be done, but the smooth curved line is baffling.
Anybody know or have done it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are just a couple example but are very cool.
Wrong thread
Mokum020 said:
This guy knows/done it and even shares the files https://plus.google.com/+LutzLinke/posts/ZdPKePpGZ3W
Click to expand...
Click to collapse
Wow thanks!! I'll have to really take a look at that and/or download it, etc.
Got to be some pretty advanced math going on there. Not rocket science type but not something I'd want to hack my way through either lol.
Wrong thread
Hi there,
Red Magic 8 Pro users, Does anyone else have this large bulb icon that's stuck at the bottom left part on the lockscreen? I'm not sure what it's related to so I don't know how to remove it. Anybody else having this issue? I hoped the latest software update that came on on Feb 22nd would have fixed it but no luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Other user reported it as a “google home” icon, sort of a bug
Alextakatu said:
Other user reported it as a “google home” icon, sort of a bug
Click to expand...
Click to collapse
Ooh interesting, well the would make sense if that is the case as I definitely use the Google Home app often. The phones so new I know bugs are par for the course so I'll just wait for the next update. Thanks for the reply!