Hi JIT,
I haven't even started looking for the black colors yet. I did take a quick look for those colors, but didn't see anything immediately obvious. I'll take a break from searching through the whites to see if I can locate them, but it may take some time.
In a quick look through some of the assembly, I noticed that some of the routines that appear to deal with string values in GUI elements don't appear to take color value parameters. So be forewarned that some of the black, dynamic text elements may not even allow a color to be passed to the display routines. Meaning, if true, that some or all of the black text in the menus cannot have a different color.
Hopefully, I'm wrong about that.
pb
Hi AcuraTLFan,
How about the well known commandline option to suppress the warning:
iGuidanceUMPC.exe nowarning
pb
Hi all,
Added a couple more color locations regarding the OSK alphabetic buttons, including the speed-alert numbers. These locations, highlighted in blue, are 2 dword locations separated by an "add" opcode ("05").
If you zero out the first 4 bytes, then skip over the "05", the next 4 bytes will be the color you want. Not particularly efficient code, but at least we can get what we need.
I still haven't located the black "current destination" text. The text seems to be drawn in the same "DrawTextA" routine that is also drawing the "Current Destination" title text, but I haven't located a color value for it. The containing subroutine has about 20 variables and calls all of the functions to instantiate and draw the window. I guess I'm just going to have to sit down and trace out each one. IDA doesn't pick up the parameters correctly because the sub is called dynamically. -- Sorry JIT.
pb
awesome with this and iGQwerty there isnt much that cant be changed now cause i dont know about you but i wanna beat the guy who made the keyboard abcd
This should be a sticky. great work
.______
| '_ |__\___
[(o)|___(o)] XB
._________
| I__I I_I|_\__I
[(o)______(o)]b VanPimpin'
LostReceptions Apps D/L Here
GPSGasoline- Rewriting
Draw- SkribblePad for Touchscreens
iGQwerty-iG3.0 Qwerty Keyboard
CarPCNetwork
Hi LostReception,
Speaking of QWERTY...
One of the first addresses I found was the Speed-Alert numeric keypad table. The address is located at 0xD5331 and contains the ASCII characters used to generate the buttons. You can actually change the following bytes and still remain in the window area:
0xD5330 - 0xD5336
0xD5338 - 0xD533E
0xD5340 - 0xD5346
There are also a few ASCII tables used for the OSK's. Just search for the text: "ABCDEFGd". The "d" is the backspace key, "hh" is the numeric keypad switch, etc. The table isn't too hard to figure out. Change the ASCII to get what you want.
Unfortunately, the existing OSK window isn't wide enough for a true QWERTY keypad, which is why I haven't mentioned this before. Yes, you can change the buttons, and the changes also enter the correct text into the edit box, but who wants a keypad like this?:
QWERTYUI
ASDFGHJK
ZXCVBNM[del]
OPL[num][sp][ok]
pb
yea i started there and ended up with what i have now cause of that problemOriginally Posted by pbarrette
hopefully Inav will listen to us on the NEXT version we can only hope (but they never do) i shouldnt say never but rarelythx again for the hard work
.______
| '_ |__\___
[(o)|___(o)] XB
._________
| I__I I_I|_\__I
[(o)______(o)]b VanPimpin'
LostReceptions Apps D/L Here
GPSGasoline- Rewriting
Draw- SkribblePad for Touchscreens
iGQwerty-iG3.0 Qwerty Keyboard
CarPCNetwork
Hi All,
Updated with more color locations.. I should have just about all of the OSK color locations soon.
The OSK edit box still has me stumped though. Anyone have any ideas?
pb
I don't think I understand the 'blue' special DWORD color rule from your list.
For example:
0x30E37 Destination - POI - Food OSK - NumPad Buttons Text (x2)
What I see in that region is this: (the bold location is exactly the address you gave)
...25 01 00 FE 00 05 FF FF 00 00 8B 11 50 FF 52...
From your exaplanation:
BLUE = DWORD+"05"+DWORD Color locations. Set first 4 bytes to 0's. Skip over "05". Set second 4 bytes to color in RGB0 format.
I don't see that pattern at all! What *exact* version of UMPC are you using?
2002 Honda CR-V
Carputer progress: 90% [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ -]
Spent so far: $1105.90
Download the NEXUS Skin for Centrafuse
...or even Listen to my music
Ah Crap,
I knew I was going to get typos in this list.
Your PM box is full, so I can't reply to yours. What I was going to reply with was this:
As I find the locations, I mark them in the WinHex position manager. When I decide to update the list, I open the position manager and transcribe the new entries into notepad. Then I add the BBCode formatting, then edit the post, pasting in the new list.
Since the number of locations has grown significantly, my typo rate has gone up as well. Also, the way the position manager works is this: When you open the position manager and add a new position, the hex offset is filled in automatically with the position of the cursor. I must have had the cursor in the wrong position when I marked the Dest-POI-FoodOSK-Numpad location. But not by much.
You found this:
25 01 00 FE 00 05 FF FF 00 00 8B 11 50 FF 52
But the location should actually be 0x30E32, where you would find this:
25 01 00 FE 00 05 FF FF 00 00 8B 11 50 FF 52
So the change would be:
25 01 00 FE 00 05 FF FF 00 00 8B 11 50 FF 52
25 00 00 00 00 05 FF 00 FF 00 8B 11 50 FF 52
That will change it from white to purple.
See that:
01 00 FE 00
+FF FF 00 00
-------------
=FF FF FF 00
I'll make the corrections you noted. If you find any more, let me know.
pb
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote
Bookmarks