Rockbox Development > Feature Ideas

%?cM %?cl tags (VISUAL CLOCK)

<< < (6/8) > >>

karashata:

--- Quote from: audio-i on January 22, 2010, 01:15:15 PM ---Theoretically, using "the magical transparency colour", that could be done with 12 images for the hours, and 60 images for the minutes.

--- End quote ---

The transparency colour doesn't work for drawing images over other images, since the transparency draws the background in place of the transparency colour (so all you'd see would be whichever image you drew overtop of the first one)...


--- Quote from: raudonkepuraite on January 22, 2010, 01:20:51 PM ---OH be more creative! (and btw Rockbox can only use 280 contitions of one tag if ui simulator is right).
THIS GOES FOR ANALOGS (I dont prefer this kind of approach for analog clocks... VISUAL CLOCK doesn't mean analog clock)
Still THERE IS NO NEED TO MAKE THOUSANDS OF IMAGES for them. You make 60 images for the minutes (its really easy as you only need to make a line and then you can just rotate it whatever you want using photoshop or even paint :D) and then you make 12 more for outer ring for displaying hours... Or you don't make any at all and just use digits to display hours. There are many ways to make it look right, you can make binary clocks if you want, morse clocks, then you can even make sun clocks (I'm just making some ideas here).

AND ABOUT NORMAL (well i mean digital) clocks

--- Quote from: bakseetdrivr on January 22, 2010, 09:31:33 AM ---2nded, I've been using one of my rockboxed players as an alarm clock and tried to make a suitable theme,  but having a huge font makes menu navigation nearly impossible. If this was committed, it would fix that problem :).

--- End quote ---
Here is one problem... but of course you are going to suggest multifonts... right? Well yeah its better to reserve additional 60kb for a huge font than use 5kb (in worse case) to make a custom clock? MOST themes aren't using even half image buffer (using like 30kb-50kb assuming that we have sansa fuze in mind). As far as i know that buffer (or whatever it's called) size is constant... right? So we lose nothing here if we use custom clocks.
Text based clocks are small, image based clock would be wonderful solution.

--- End quote ---

As I stated above, you can't draw one image over another an have the bottom image still displayed, even with the transparency colour, so you couldn't use your idea for an analog clock...

I hadn't taken into account morse clocks or other styles of visual clocks, but those would likely still have the drawback of taking up a lot of screen space, especially on the smaller screened DAPs... (Plus, those could be pretty confusing for anyone who doesn't understand them...) As for the digital clock, there is JDGordon's patch, wherever it went... It would probably need some work done to it to work with the recent code...

The text based clock is only as small as the font used to display it... Assuming the clock uses the UI font, it should be just as easy to read as the rest of the UI, if it's using the built-in system font it would definitely be hard to read on the larger screened DAPs with their higher DPI ratios... On the smaller screened DAPs with lower DPI ratios the system font is still quite readable...

raudonkepuraite:
Gee, didn't I write outer ring? Well I meant square. Do you get it now?...  I just don't know how to explain you this, anyway lets leave those analog clocks for a while, ok?
Transparency colour is useless anyway (except when using %x tag, but the image then is "solid"... you cant do anything with it). This is huge problem for themers as well, believe me, it's one of the main problems why rockbox looks so... dev like (actually it looks worse to me ^^)
The problem is that text based clock IS only as small as the font used to display it. So if you want bigger clock you have to use bigger font... BIG FONTS SCREW UP EVERYTHING. Try putting 35px height font on 360x240 or 220x176 screen... veeery readable, isn't it?

edit: BTW, I want to test the patch provided by JdGordon... this might sound stupid, but is is there any possibility that I might brick my player  :-[ ?

audio-i:

--- Quote from: karashata on January 22, 2010, 01:51:58 PM ---
--- Quote from: audio-i on January 22, 2010, 01:15:15 PM ---Theoretically, using "the magical transparency colour", that could be done with 12 images for the hours, and 60 images for the minutes.

--- End quote ---

The transparency colour doesn't work for drawing images over other images, since the transparency draws the background in place of the transparency colour (so all you'd see would be whichever image you drew overtop of the first one)...

--- End quote ---

Have you tried it? In this simple example you'll see what I mean


Background + image 1 + image 2 = final image displayed

raudonkepuraite:

--- Quote from: audio-i on January 22, 2010, 02:32:28 PM ---
--- Quote from: karashata on January 22, 2010, 01:51:58 PM ---
--- Quote from: audio-i on January 22, 2010, 01:15:15 PM ---Theoretically, using "the magical transparency colour", that could be done with 12 images for the hours, and 60 images for the minutes.

--- End quote ---

The transparency colour doesn't work for drawing images over other images, since the transparency draws the background in place of the transparency colour (so all you'd see would be whichever image you drew overtop of the first one)...

--- End quote ---

Have you tried it? In this simple example you'll see what I mean http://www.fileden.com/files/2008/2/11/1754365/test.zip (ipod video)


Background + image 1 + image 2 = final image displayed

  + + =

--- End quote ---

This wont work with anything that has tags (I had already tried it with custom volumebars and seekbars)

karashata:
The last time I remember ever trying to draw images over other images (or text over images), the way transparency was handled was to draw the background in place of the transparency colour regardless of whether an image (or text) was overlapping another image. That may have changed since the last time I tried it though...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version