Hi
Does anybody know where the skins are for the signal strength button the connection state button and the volume button are.
As you can see in the image below im trying to set a green theme with the txt on my exec and these icons don't go as they are white.
Many thanks
Scott
There built into some of the ROM dlls I think. Most people skin the bar with WisBar or similar.
V
I Suspected as much that these were related to dll's
Does anybody know which dll's they are.
I did use to use wisbar but i found that there was just to much lag with it.
I would like to know this to as i also think that wisbar lags up the device to mutch
Anybody got any ideas.
I think if we can crack this 1 it may also helps us understand how to remove the dam battery icon in the new imate rom and let us put the clock back.
shellres.96.dll
V
Microsoft design guidelines demand that these symbols remain white... Not that this will stop you but I thought you should know.
lbendlin
Is there anything on this board that is within the Microsoft guidelines!?
V
vijay555 said:
lbendlin
Is there anything on this board that is within the Microsoft guidelines!?
V
Click to expand...
Click to collapse
This looks kick ass! When did you cook this one now???
San, that's a screenshot from VJSmallIcons II, which will turn your "programs" launcher fullscreen and permit changing the view style (look up VJSmallIcons to see what the original did). The new version, although looking simple, requires a lot of voodoo in the background, but it's a test platform for stuff I'm developing for VJToggleToday II.
VJSmallIcons II should be out quite soon, just one or two more tweaks to retain settings in the registry and it'll be out for test releases.
scotjen1: to come back On topic, I've never tried overriding that dll, but I presume you could try the same technique used by Azhad here:
http://forum.xda-developers.com/viewtopic.php?t=34995&highlight=
to create a new resource dll to override the original icons etc. It'd be a nice hack to try.
V
V
Great work with VJsmallicons II looking good.
Now back to the skinning. I have managed to copy the shellres.96.dll (great work for that V would have never known that) to my desktop and have used resource hacker to extract the ico files from it.
I then found a program called easy icon maker (good program works well) and have managed to change the colour of these icons.
When i then replace the resource with resource hacker it show as if it has been replaced i then load the DLL back in to the windows dir and get an error saying this file is in use and can't be overwritten but i use resco and it gave me an option to continue which i presume forces it to be over written. I then soft reset and bang the icons are exactly the same. Any idea's ?
Also just 1 other thing when changing the icons they were set to 16 x 16 and 2 colours so i had to change this to 16 x 16 and 16 colours would this have made a difference also.
scotjen1: it's likely to be more involved then that (as if that wasn't enough!).
You will have to have a read through Azhad's thread above, and the VGA files thread. What you need to do on WM5 is, I believe, although I have no direct experience in this area, is to create a resource only dll containing the icons you want to replace. 16 colours should make no difference. But I believe the resource ids need to match the original.
That needs to be signed (check the first few VGA files posts for info of how this was done originally, and find the signer, called SignIt, posted by BeyondTheTech I believe), and then save the file as an .mui file so that it gets loaded over the top of the original shell file. That shell file is unlikely to be replaceable whatever Resco thinks.
Have a read through Azhad's thread, decompile his .mui files and that should point you in the right direction.
V
V
Wow that does sound quite a challenge still though im not going to let it beat me lol.
I have got Azhad's files at home (i presume you are talking about the power backlight and wifi files) i will have a go at trying to decompile them tonight see if it can shed some light on the situaion.
As for the signing wasn't there a cab flying around somewhere that disabled this or am i completly going off track here.
You still need to sign the dlls for WM5.
SignCode:
http://forum.xda-developers.com/viewtopic.php?p=191136#191136
I really can't say if any of this is correct, as I said, it's something I've thought about but never bothered with. I'm working on my own skinner for the bar, but this method should be effective + no overhead.
You don't need to decompile Azhad's stuff, just resource hack it to see what he's put in the dlls. In fact, use his dlls, empty it out, stuff it with your stuff and re-sign.
V
Nice that sounds a little bit easier lol.
Will give it a try when the work day ends will keep you posted on the progress.
Hello,
I can use TransparentBlt (or various BitBlt's creating a mask, drawing with SRCAND and SRCPAINT) to display an hbitmap without a background, and I can use AlphaBlending to display an hbitmap partially transparent (a fading image).
I'm having trouble, however, using both at the same time, i.e. display a fading image without its background.
I've tried functions to copy an hdc to a hbitmap (which I can give to AlphaBlending) with no success (most "working" versions I found with google seem to CreateCompatibleHdc, CreateCompatibleBitmap and then start to BitBlt the empty bitmap... It produces horrible results here).
I've also tried AlphaBlending to a TestHdc, displaying a mask in the FinalHdc and BitBlt'ing the TestHdc to the FinalHdc, but I don't know how to do it correctly: I've been using SelectObject(TestHdc, Image); and SelectClipRgn with both a fullscreen rectangle and an imagesized rectangle to no avail.
I'm interested in knowing if there's any way to do this, and how.
Can anyone help with this?
Thank you very much!
lol, I have the exact same problem! hope someone has an answer..
Shoddy_me said:
lol, I have the exact same problem! hope someone has an answer..
Click to expand...
Click to collapse
IImage allow you to do that, but it's slow as hell (like alphablt in fact).
Look at DIB section, and do it yourself, with the proper optimization it should run fine (and it allows you to do real transparency).
28-08-2008
Click to expand...
Click to collapse
I went with IImageFactory until I didn't need it anymore (too slow, but IImage supports png with alpha) Thank you anyway
I'm just fed up with this wallpaper issue in Manila.
When I got my Touch HD I figured someone will figure out why exactly is the 800x400 screen reducing wallpaper image quality to some low-res sh*t.
But, it's been months now, and no one seems to be working on this, so what the heck - I've decided to post it here, in hope that someone will actually try to do something about it.
What really disappointed me was the fact that even the latest Manila 3 from Topaz and Rhodium still has the exact same issue. So, it seems obvious to me that guys from HTC have no intention of fixing this. Why? I don't know.
But I do know it's frustrating to have all those fancy graphics, all that big, high-res screen, and then be forced to stare at THAT all day long.
Since I've seen so many great things being done to improve Manila, such huge changes to the whole system, I reckon there must be a way to improve this as well.
p.s. If no one cares, just take this as a bunch of rambling from a visual kind of guy
Oh, and just to share my info so far:
- the wallpaper picture format has no impact (I have tried them all - jpg, png, gif, bmp, 8 bit, 16 bit, 32 bit etc.)
- wallpaper picture size has no impact (it will look just as bad if you use 640x480, 800x400 or 8000x4800 pixel)
- if you put 800x400 wallpaper, it will not be stretched in any way - it will fill up the screen exactly 100% full, so people reporting 640x440 photos having better quality when used as wallpapers were having a placebo effect.
- the default Manila wallpaper is crisp sharp - no trace of any quality degradation.
- all default Manila wallpapers are very simple looking, with small number of colors, and very short range of colors (mostly it's just shades of gray and black)
- TF3D obviously applies some kind of compression algorithm to any applied photo, increasing brightness and applying very, very, very agressive image compression.
I believe it is this compression that is the cause of the image degradation. If someone could find the registry key to turn it off, I assume the problem would be solved. I also have a feeling that this compression was pushed up so high in order to speed up TF3d.
I am attaching an enlarge example of this compression. Original wallpaper vs. how it looks on TF3D.
I have no idea if I should move this somewhere else..
so Rozenthal, is this meant to be a development thread?
Well, more of a "hacking" if you want. If an application would arise from this, it would sure be great, but tracking down the problem itself and finding a manual solution would be also very much appreciated.
I posted this into this forum because I figure here's where most of the people dealing with Manila graphics are hanging out.
Bla, fixing up my CFC patch for Manila to be able to load PNGs would possibly solve this. However I seem to recall something about the background always being shrunk to 512x512 max with the vertexes then stretched to fill the screen. Not completely sure on that, though.
And yes, QTC compression (used for Manila) is definitely lossy. It can be pretty decent though, depending on the editor you use.
Chainfire said:
Bla, fixing up my CFC patch for Manila to be able to load PNGs would possibly solve this. However I seem to recall something about the background always being shrunk to 512x512 max with the vertexes then stretched to fill the screen. Not completely sure on that, though.
And yes, QTC compression (used for Manila) is definitely lossy. It can be pretty decent though, depending on the editor you use.
Click to expand...
Click to collapse
Chainfire, you must be reading my mind! I was just now reading that thread of yours where you used CFC to resize images for QVG and was going to write to you
I believe that information you provided in that thread MUST be somehow linked to this problem. I have only skimmed through your thread, but from what I understand there is in fact a compression algorithm involved in all Manila graphic files?
About the 512x512 - I can almost certainly say that this is not the case in Touch HD. The images you use for wallpaper do not get scaled in any way if they're in 800x400 resolution. They stay the same (this was the first thing I tested). However, they do seem to go through some sort of compression that causes any kind of graphic to look bad.
So, you're saying there's a way to manually compress with better results? But what then? How do we apply the custom-compressed image? I'm guessing it would be necessary to first find out which file is the default Manilla wallpaper, and then replace the new one with that? Would that work? Can this somehow be automatized?
I know it's a lot of questions, and it's late, but any help would be appreciated, especially because I feel that this might be the closest we got to solving this damn problem.
Cheers!
Have you tried interlacing your .pngs? I realized that interlacing my images for manilla 2D themes helped. I was also under the impression that HTC has some special compression going on with their images, but while saving my images in photoshop, I save them in .png and select interlace option in the end. Try it.
Here's what's up:
1. When you save images for your pocket PC, they DO have to be in a loss less format, such as .png... This goes for Homescreen backgrounds as well, so when you save a picture off your phone camera, it'll be pixelation by default because they're usually in .jpeg format.
2. When you save images in Photoshop, in a format like .png. Save them as Interlaced images, or they'll come out crappy on the device.
3. If you are using the color overlay feature in Photoshop to, say, change the color of the image, There will be pixelation if there are any gradients in the picture. Most of the images in the Manilla 2D theme files have gradients, so almost all of them result in pixelation. What you have to do for those is: Zoom in and use the Blur tool (Smart Blur filter on larger images.) to smooth out the pixelation!
Hope this works for other people, and if someone can contribute anything else, it would also be appreciated.
The screen is 800x480 isn't it?
yes it is 800*480
makes me feel bad that it looks like that on such a beautiful device.
its obviously unacceptable that HTC playes like that.
i dont understand whats their big problem to give us some drivers that would solve this annoying issue
Here, try this file out. Make a backup copy of yours unless its cooked in rom, that way you can delete this if necessary. It makes a difference for me. In this section of script, I changed the values to 200, 200 and it was reeeeeally crappy. I did that when I was checking effect. Originally it was 512, 512. In this one, I made it 800, 800.
I think it also makes bg's better if you make them square(in my case 640x640), especially if your using the new landscape manila. I know on touch pro, the rotation works better with bg's that don't have to be stretched.
BackgroundAsyncImageFactoryLoader = AsyncImageFactoryLoader()
BackgroundAsyncImageFactoryLoader.Priority = TaskPriority_BelowNormal
BackgroundAsyncImageFactoryLoader.Quality = 100
BackgroundAsyncImageFactoryLoader.OnComplete:connect(BackgroundImageResized)
BackgroundAsyncImageFactoryLoader:ResizeImage(machineStatus.HomeBackgroundPath.Value, CachedImagePath, EncoderType_JPEG, 800, 800, true, false)
Click to expand...
Click to collapse
Does anyone know what the true, false is at the end of that line?
Re Wallpaper Resolution
I'm sorry but the Wallpaper you have as an original is of such poor quality that no phones resolution could correct it. I have a Touch HD myself and have made many Themes for all different phone resolutions and now for my new phone as well and have never had trouble getting what I expected and I use all of the graphic formats ie: .png .jpg etc.
For WVGA the Backgrounds actually need to be 480 x 696 for portrait and 800 x 366 for Landscape, what has not been taken into account is the size of the top and bottom bars which are both 52 pixcels adding up to 104 pixcels this needs to be subtracted from the overall size.
http://forum.xda-developers.com/showthread.php?t=492857&highlight=touchflo+vista
stickfigure said:
Have you tried interlacing your .pngs? I realized that interlacing my images for manilla 2D themes helped. I was also under the impression that HTC has some special compression going on with their images, but while saving my images in photoshop, I save them in .png and select interlace option in the end. Try it.
Here's what's up:
1. When you save images for your pocket PC, they DO have to be in a loss less format, such as .png... This goes for Homescreen backgrounds as well, so when you save a picture off your phone camera, it'll be pixelation by default because they're usually in .jpeg format.
2. When you save images in Photoshop, in a format like .png. Save them as Interlaced images, or they'll come out crappy on the device.
3. If you are using the color overlay feature in Photoshop to, say, change the color of the image, There will be pixelation if there are any gradients in the picture. Most of the images in the Manilla 2D theme files have gradients, so almost all of them result in pixelation. What you have to do for those is: Zoom in and use the Blur tool (Smart Blur filter on larger images.) to smooth out the pixelation!
Hope this works for other people, and if someone can contribute anything else, it would also be appreciated.
Click to expand...
Click to collapse
Of course I tried. I tried interlacing both PNG and GIF's, I also tried different color depths, and all supported picture formats. It had no impact.
The thing is images don't look crappy on the device - when you view them in Album application, they look excellent. Actually, they look better then on my 30" Apple cinema screen, because HD has such huge pixel density.
However, when you apply these images to act as wallpapers on Home screen, they drop in quality and sharpness so much that it degrades the whole device appearance. And this is very annoying
grzegorz10 said:
I'm sorry but the Wallpaper you have as an original is of such poor quality that no phones resolution could correct it. I have a Touch HD myself and have made many Themes for all different phone resolutions and now for my new phone as well and have never had trouble getting what I expected and I use all of the graphic formats ie: .png .jpg etc.
For WVGA the Backgrounds actually need to be 480 x 696 for portrait and 800 x 366 for Landscape, what has not been taken into account is the size of the top and bottom bars which are both 52 pixcels adding up to 104 pixcels this needs to be subtracted from the overall size.
http://forum.xda-developers.com/showthread.php?t=492857&highlight=touchflo+vista
Click to expand...
Click to collapse
The image I attached is 600% blown up version, that's not full size wallpaper.
And it doesn't matter what kind of quality of image I use - the images always appear much less sharp and with reduced quality when applied to home screen wallpaper.
Also, I don't think you're right about 480x696. That is the "visible" area of the screen, but homescreen wallpaper will always be used in 100% if the width is 480 or height 800. It might get cropped tough, can't say that for sure.
But, for example lets say you want to use image that is 800x800 in original resolution. When you set it as wallpaper, it will not be resized to fit 696 height, but rather it will be cropped on the sides, and the top and bottom bars will cover the top areas of the image. But there will be no scaling involved. This can be easily tested simply by overlaying the original image over the captured image of the device.
showaco said:
Here, try this file out. Make a backup copy of yours unless its cooked in rom, that way you can delete this if necessary. It makes a difference for me. In this section of script, I changed the values to 200, 200 and it was reeeeeally crappy. I did that when I was checking effect. Originally it was 512, 512. In this one, I made it 800, 800.
I think it also makes bg's better if you make them square(in my case 640x640), especially if your using the new landscape manila. I know on touch pro, the rotation works better with bg's that don't have to be stretched.
Does anyone know what the true, false is at the end of that line?
Click to expand...
Click to collapse
Hey, thanks! I have tested this, using 640x640 images, as well as 800x480, and 800x800. I can't say if it's a placebo effect, but the image does look slightly better.
Could I ask you to make a few versions of this file with parameters that can be substracted by 512? Because if I remember correctly, Manila likes those 512 numbers. So, if you would be so kind to make 1024x1024, 1536x1536, and 2048x2048.
I would be glad to test them to see if there are any further improvements over this issue.
Ok, I tested everything again with a different wallpaper, so there's no more question whether the source file is good quality.
I think this image is suitable, because it has a lot of small details, but also large areas with soft transitions, so we can see the effect of compression on both the detail and the textures.
I also tested 696 file, and as I said earlier - it has absolutely no positive effect to image quality.
I have also noticed that in fact even the HTC Album applies some sort of image compression, but it's much much less visible! You can notice the effect of this on the dark area transitions. However, it's barely noticable when viewed on the device.
Perhaps if someone who knows where the HTC Album Manila files are, maybe it would be possible to compare them with the files that control compression in Home screen? Perhaps it would be enough just to copy the settings for HTC Album? Just an idea...
I'm attaching the files, they speak for themselves.
ok i've search in the registry with:
compress
quality
jpg
wallpaper
desktop
but nothing
BadCluster said:
ok i've search in the registry with:
compress
quality
jpg
wallpaper
desktop
but nothing
Click to expand...
Click to collapse
So did I Same results.
I don't think it's that simple anymore. We probably need to combine 2 things: the edited Manila file to support graphics up to 800 pixels, a way to easily compress a photo with ATC compression and then make Manila use it.
OK, I think I finally figured out some stuff. First of all, we knew from before that wallpaper image for landscape was made out of 2 bitmaps.
However, it seems that this is the same case with the portrait wallpaper as well.
Digging through Manila graphic files I've found that indeed the maximum image size is 512x512pixels. So, in order to get the 480x696 pixel needed to cover the whole visible screen area, guys from HTC simply used 2 images, each with 512x512 resolution, but first actually covering 480x512 area, and the second 480x184.
Together, as you can see, they make 480x696.
But, what happens when you load 800x400 pixel image?
Most likely that the image first gets cropped to 480x696 dimensions, and after that top part (480x512) is put into one file, and the bottom part (480x184) is put into a separate file. They both get compressed with that ugly algorithm and that's why we end up with crappy looking wallpaper photos.
Files involved are:
LANDSCAPE:
29cff4fe_bglevel0_landscape_left.png
058acf31_bglevel0_landscape_right.png
PORTRAIT:
70083a29_bg_level0.png
77feee1d_bg_level0_bottom.png
Now, it's clear that Manila indeed does support full resolution, but because the wallpaper is being split into 2 parts and compressed, we have poor image quality. What brings us back to my first idea - is there a way to disable this compression, or increase the quality of the compressed photo by somehow forcing the compression algorithm to produce higher quality images?
Another way would be to use a Manila editor, cut the images into 2 manually, update old Manila default wallpaper files and always use the default background.
This is of course major pain in the a$$ to do each time you want to simply change a wallpaper.
Oh and by the way, for the record, I just manually updated these Manila graphic files, overwrote the old ones and I'm looking at my full-resolution wallpaper right now.
So, this obviously can be done. The question is can it be automatized?
this is a tricky subject.. well i've always edited the 4 manila files to create my wallpapers on my Raphael.. well i also tried background for all tab but that's kinda buggy in the prosess of when i change from portrait to landscape.. well it's like the background for all tab app kinda takes the image i want as background and overlap the 4 manila files that has to be edited manually to make a great background,... well anyway i'm stuck with the same thoughts as this thread states... it's not so fun to always have to edit those manila files to create a good background and so forth...
For those who know what it is, I have created a complete install for the HP 48GX Emulator optimized for WVGA devices. The emulator itself is based on Sébastien Carlier's Emu48 (now maintained by Christoph Gießelink).
My goals were to have a realistic but finger-useable HP 48GX. I have included the complete package in a single CAB (the ROM is an HP 48GX-R model). As HP released the ROMs for all the 48 models about 9 years ago, I can't imagine them complaining that I'm packaging them together as a useful package these days
See the attached Todo.txt before posting any bug reports please. FYI, I do not really plan to address any of the Todo items anytime in the near future.
Enjoy!
HP 48GX-R 1.18.1
Change Log
2009.09.24
v1.18.1
Converted 709 KB bmp file into 94 KB gif with no data loss. The screen should now load much faster.
Updated CAB file installation to allow for Storage Card installation.
P.S. The thumbnail doesn't even begin to do it justice. I spent *DAYS* on the visual appeal of the interface and for anyone who owns/owned an HP 48GX I hope you'll agree the level of detail and realism is nearly perfect.
P.P.S. If you don't know what an HP calculator is, or more importantly what RPN means, then its probably not worth your time even trying this.
48GX State Files
I have now attached some state files which includes two .e48 files and a SHARED.BIN file. The SHARED.BIN file is a 512K Port 2-5 attached card which both .e48 files share. The files are as follows:
SHARED.BIN
Port3
EDFlags 2.0G
HPTabs (Part of the Jazz package, see below)
Hack 9.4.1 (Based on Hack 9.4 with my own customizations)
StringWriter 4.4
MiniWriter 1.2
SmartKeys 1.59
Port2
Unitman 7.2001
QPI 4.3
ALG48 4.2
ALG48_SpecialFunction 4.2 (Part of the ALG48 package, see above)
ALG48_LongPrecision 4.2 (Part of the ALG48 package, see above)
ALG48_SymbolicIntegration 4.2 (Part of the ALG48 package, see above)
ChemLab 2.7
Neopolys 6.5
Bode-Routh 7.1
HP 48GX-R Math.e48
Port1
Erable 3.201 Beta
Marable
Erable_MODULO 3.2 (Part of the Erable package, see above)
Erable_GEO 3.2 (Part of the Erable package, see above)
Erable_PREP 3.2 (Part of the Erable package, see above)
Erable_LIN 3.2 (Part of the Erable package, see above)
Matrix 1.2
MathTools 7.0
Universal Font Library 1.0.2
Port0
Java 3.6a
HP 48GX-R Dev.e48
Port1
Jazz 6.8
Universal Font Library 1.0.2
MathTools 7.0
Matrix 1.2
Port0
Java 3.6a
Included in the zip is a file called InstallConfigure.txt which is simply the steps I took to create the .e48 files. Please note that I did not include the application .lib files themselves, though I did link most of them above. Remember, you can always recall them to the stack and save to your device if you plan to use any of them to make your own state file(s) from scratch.
48GX WVGA Photoshop Source
If your goal is to modify the visual appearance of the calculator without modifying the position or operation of any of the keys (onscreen or keyboard) then you may be interested in downloading the Photoshop source (attached).
Using it you must create a BMP file that is dimensionally identical to the one included in my installation (else you must change the KML appropriately). This means that there must be the entire image with no buttons pushed followed by the annunciators, followed by an image with the buttons pushed (without the annunciators again though). See the BMP that comes with the installation to know what I am talking about here.
The photoshop source is currently set to output an image with no buttons pressed and the annunciators. You will save as a BMP image to get the initial image with annunciators. You must then hide all the appropriate layers (and there are MANY) for unpressed button mode, and finally show all the appropriate layers (again there are MANY) for pressed button mode. Now change the image canvas size (cutting 14 pixels--the annunciators) from the bottom of the image, and save this as a BMP image. You will then take the first BMP image, expand the canvas size by 748 pixels at the bottom, adding the second BMP image (with the pressed buttons) in that area. Then simply merge layers and convert that image to Indexed color mode (selective) and save as the final BMP image.
If you are planning on changing colors note that where possible all you have to do is select every appropriate text layer and then change the colors for all of them at once. However, you will notice there are two layers (one for text graphics, and one for button graphics) that you cannot do this. You may deal with these in one of two ways:
Use the wand tool selection with shift to select all items of a given color, and then use some form of Image|Adjustment|... to match the colors.
Recreate the items manually. This is where the HP48.csh file comes into play. These are vector items I created for some of the button graphics (and annunciators). Access them through the custom shape tool (load custom shapes from file).
The button pressed version of the button graphics is precisely the same as the non-pressed version, simply shifted down one pixel. So my recommendation there is to simply make changes to the non-pressed version, duplicate it, shift down one pixel, and make that the new (Pressed) layer.
If you spend the time to properly create a graphics file that you think others would enjoy, please upload it and the source for others!
Cheers!
I still have my 48gx from more than 10 years ago, now I am just a HP12c type of guy
Excellent Work! Much appreciated! I also have a Emu48 version used by a company called EaglePoint (used to be SMI). It is called Pocket SMI v8. I have a licensed version but it is no longer supported. It is basically a custom tweaked Emu48 with a different skin and kml script specifically for surveyors/engineers. I would like to modify the skin but I am not sure how to get started...
Very Nice! Thanks much!
You think you can skin it for my 48SX as well?
The GX colors annoy the heck out of me...
wow, I haven't tried it yet but will, awesome idea. I still have my 48GX from college but I doubt my professors would like me to use cell phone during tests.
Thanks, will try it.
Thanks!
Quentin- said:
For those who know what it is, I have created a complete install for the HP 48GX Emulator optimized for WVGA devices. The emulator itself is based on Sébastien Carlier's Emu48 (now maintained by Christoph Gießelink).
[...]
Click to expand...
Click to collapse
AWESOME!!!!
glhs509 said:
Very Nice! Thanks much!
You think you can skin it for my 48SX as well?
The GX colors annoy the heck out of me...
Click to expand...
Click to collapse
If you have Photoshop and some time/know-how to make minor changes (difference in keys) to the KML file I can provide you with the graphics source that you can work with to make an SX skin.
Thank you!
This is fantastic, I will be looking for any updates and improvements. Will test and report back.
Wow... that's amazing...
...Here's my HP 48SX from my college years (circa 1992) for comparison...
glhs509 said:
Very Nice! Thanks much!
You think you can skin it for my 48SX as well?
The GX colors annoy the heck out of me...
Click to expand...
Click to collapse
See the original post now for the Photoshop source files!
Version 1.18.1
For those that subscribe to the thread, this is notification of a new version in the First Post.
Change Log
2009.09.24
v1.18.1
Converted 709 KB bmp file into 94 KB gif with no data loss. The screen should now load much faster.
Updated CAB file installation to allow for Storage Card installation.
Thanks a lot for this.
If anyone doesn't know there is a HP Calculator Conference in Fort Collins, CO next weekend.
http://holyjoe.net/hhc2009/
help on resizing the skin hp48gx
I have tried to resize it with photoshop, but I don't know how to remap the keys.
Could be a way to include scroll bar option?
Thanks
I don't know when or how but I've ended up with some crappy barely readable fonts in my Google Map and Facebook application on my Sprint TP2.
They look very much like the type of font you see on a LED seven segment display with the space between each segment.
Can anyone tell my how to change the fonts on these two applications. I'm thinking it must be a registry entry.
Thanks.
crites said:
I don't know when or how but I've ended up with some crappy barely readable fonts in my Google Map and Facebook application on my Sprint TP2.
They look very much like the type of font you see on a LED seven segment display with the space between each segment.
Can anyone tell my how to change the fonts on these two applications. I'm thinking it must be a registry entry.
Thanks.
Click to expand...
Click to collapse
Yep, this happened to me after installing some apps.
Just find a font you like, and replace the ones in the fonts dir in windows. I used comic sans and renamed it to what was in the fonts folder and over wrote them. This will fix your problem.
Jeff
crites said:
I don't know how
Click to expand...
Click to collapse
I had the same problem after installing MS Reader. The problem is Google (and I'm guessing Facebook) use the first font listed alphabetically in your Windows dir. Least it sounds like you can see the words, I ended up with a whole bunch of characters that looked like +x0 overlapping like a LCD diplay with each segment lit.
You could try finding all the fonts on your system, working out which one comes first alphabetically, then making a copy of a font you like and renaming it to be alphabetically first. Unfortunately, even if you systematically uninstall everything, I think the font will remain so the copy/rename method is your only option. Or you could hard reset (*warning, you will loose everything!*) then inspect each CAB file you install, removing any additional fonts they contain. If you're not sure how to do that last sentence, or don't have the software to disect CAB files, it's probably best you don't go down that route!
Culprit seems to be TouchWatch2. Guess I'll either delete it or get good at switching fonts.
Thanks for the help.