Support and General Use > User Interface and Voice
While Recording Screen - User Interface Discussion - including remotes
Davide-NYC:
Mmmm, if you give me exact sizes for everything I will generate icon code for you with nice readable icons even on teeny targets like the Recorder.
I know that the statusbar is 8 pixels high, with the bottom pixel being generally blank. (The "Q" being an exception, poking down to the eigth pixel.) Just tell me how wide everything should be on the Recorder screen.
* Battery
* Volume (Now Ecoding Type and Bitrate)
* Stop/Play/Pause/Rec/FM
* Repeat (Now Samplerate)
* ? (Now Stereo/Mono icon with room to spare?)
* RTC
Questions:
What is displayed between the stereo/mono icon and the RTC in the statusbar?
If nothing then we can afford slightly better stereo/mono icons and maybe a tiny bit of breathing room.
I'm hoping with a tiny bit of refinement we can get the RSB (recording status bar) looking really slick. See gifs below:
[attachment deleted by admin, too old]
Mmmm:
--- Quote from: Davide-NYC on September 02, 2006, 11:31:33 PM ---What is displayed between the stereo/mono icon and the RTC in the statusbar?
If nothing then we can afford slightly better stereo/mono icons and maybe a tiny bit of breathing room.
--- End quote ---
I'm afraid that all the space is used up, the bit of space you refer to is used for the hold icons, and the space after the battery icon is used for the charging icon...I was initially excited about these too, but they are used!
If you look in statusbar.c you can see all the sizes near the top in the #define lines.
What do you feel is unclear at the moment? I thought MQ3 might look better as Mq3 instead... I have actually used the system font for the sample rate and Q value. We're only using icons now for bitrate on SWcodec targets, as the font wouldn't fit and channels.
Davide-NYC:
I think that bitmaps in the statusbar are the way to go from an esthetic perspective.
They give a nicer more even look and tell the user that they are not modifyable while recording.
Harder to read true, so maybe a bit less functional, but less 'crowded' looking. I would use them for the HWCODEC targets too, since they have the teeny screen.
My 2 cents. As usualy I come bearing gifs -->
[attachment deleted by admin, too old]
Davide-NYC:
After playing around in some image editing software I have changed my mind about the Archos targets.: The system font works better. :P
I guess it's the non-symmetry on either side of the play/pause/stop/rec/fm icon that bothers me... so I still think that the samplerates on the SWCODEC platforms should be displayed with a bitmap of the same height.
Any body else agree? Am I nit-picking?
Mmmm, I made a couple of changes to your patch...
Huge thanks and respect to the devs in IRC.
PATCH -->> Check it out.
I used a blocky font becuse at that tiny size it's easier to read.
[attachment deleted by admin, too old]
Mmmm:
Ok...brace yourself..here goes....
Why have you changed main.c?
I'm confused as you seem to have added a setting to settings.c which should already be there... I'm surprised it compiles.
in statusbar.c you seem to have re-enabled the volume display for non swcodec targets.
It appears that you have merged one of my old patches with your changes...is that right?
all you should need to change are statusbar.c for the display of bitmaps for swcodec tasrgets (the stuff near the bottom) and icons.[c,h] for the new icons.
Well done on making your first patch though... maybe I'll commit it if you get it fixed up...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version