hi,
I've try to understand watch face structure, but stuck on frame decoding. can anybody help me to figure out how it works?
at this time I can allocate frames and it's lines, seems figure out with palette, but cant understand line construction.
I wrote a little app to display data a bit more representative, so for sample:
{
"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"
}
in frame definition it have a two bytes what I have a smooth understanding ("09" and "03" at screen).
seems first ("09") defines a palette type (1,2 - no palette), and second means a coding type. (0 is a plain, 3 is a some sort of compression)
so plain frames are ok, but I can't understand compressed lines.
as I understood, first 12 bits (1.5 byte) of a line, is a some count <= frame width. pixels defines as color id in one byte, but that's all.
can anyone help me figure it out?
app and few wf'ses are attached in zip
n.m. figured out:
Related
I've tried several times to ypload screen shots of my Today screen, and each time I'm told the file can't be re-sized, the file I'm trying to upload is 240x320. Why is it others can upload screen shots of their Today screen, and I can't? Is this a priviledge for senior members, moderators, developers,etc. only? Hell what size is the display of their device....115x176?????
8125 (2.8" 240x320)
just because ur screen size is 240x320 doesnt mean the picture is...
{
"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"
}
<just to tease.. ...>
Madcap180 said:
just because ur screen size is 240x320 doesnt mean the picture is...
<just to tease.. ...>
Click to expand...
Click to collapse
Yeah, but the message I get says the image is 240x320. First it says the limit is like 620x280, just don't make any sense to me at all! I believe 240x320 falls well under that limit. Something's screwed up!
8125
Apparently trying to upload bitmap images was the problem. I found an app called LOOKMobile that saves the btmap image, and when the image is saved, the image becomes a jpeg file that can be uploaded from here.
8125
Hello there image editor pros!!
I have a simple request.. I am in dire need of an alteration to an image.
My customized taskbar is almost complete with the exception of my signal icon.
Attached is a 32X32 - 32bit signal icon. I need this resized to 16X16 - 32bit depth.
I have tried to resize it using IcoFX but the image, because it's being resized to a smaller dimension, always comes out blurry and grainy and just doesn't look good on my taskbar.
Below is the example of what it looks like (notice the fuzziness):
{
"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"
}
And this is what I want it to look like (notice the clearness):
I'm just talking about the SIGNAL ICON ONLY not the bars!
If one of you design editors could edit this image for me, successfully, I would be very greatful.
Please do not ask me why I didn't do it myself, because believe me - I tried a lot and just wasn't able to edit it down myself.
Also, the reason I can't use the 32X32 - 32bit icon is because I am using a CDMA version of the HTC Touch Diamond and it does not read from the same .dll file for the icon.
Any other questions, just post them.
Thanks in advance for any of you who respond.
-HTCLeener
Hello,
I've reading the topic About Avoid Creating Objects in Designing for performance for android and says:
When extracting strings from a set of input data, try to return a substring of the original data, instead of creating a copy. You will create a new String object, but it will share the char[] with the data.
I don't understand it. Maybe I have to get a book of java, jeje.
Well, it's difficult to find information about this paragraph.
Could you write an example or explain it?
Thank you.
How I understand your quote, it works like show in this image:
{
"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"
}
The above method is the suggested one. Here the returned substring of the original string still points internally to the original char[] array so there is no memory wasted.
In the second method a (shortened) copy of the original string is made, so you are wasting (in this example) 6 more bytes of memory.
Thank you.
Now I understand. In the better option you reuse the same array. So there is no need to create a new object.
My intention here was not to build something that folks would use, but rather to experiment with "animation", or moving things around as time, date, battery level, etc. changes.
This has 8 animated items.
The temperature, battery level and minutes just sort of click from one value to the next. I tried to use seconds for the minutes to make a smoother step, but it just does not work well.
The day of the week, hours, AM/PM, Month and day of month are more animated. The background numbers rotate into view and when the next increment reaches the static white value, it clicks over to the new value.
The hour and AM/PM are full circles with the values at their representative slots. The others move value in from off screen, then continue off the other side.
Most of these move in an arc, but the day of the month moves in a line.
Hopefully this will help some folks and give some of the more creative types out there some ideas for some cool new widgets.
Swoops.zw
{
"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"
}
(Next up: I almost have numbers in a "behind frosted glass" look working).
So I made this 3D Live Wallpaper for the fun of it and thought I should share it with other LineageOS fanboys/girls. This probably works on other devices too.
I have no affiliation with the LineageOS team.
{
"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"
}
Feature/info:
-Small. . . Like 27 lines of code.
-Draws every other frame.
-3D asset is also small (<150kb)
-Anti aliasing x4
-No ads
-See second post for change log.
Design decisions:
-Solid background so we aren't drawing lots of complicated things every frame.
-Logo has been re-designed in Blender it looks much better now.
-The spin(s): I have the spinning tied to the framerate at the moment. I feel this is better than adding more math.
If you have any suggestions or requests fire away.
Change log:
1/9/17:
-Logo completely re-designed.
-Background changed to fit LineageOS color scheme.
-Lighting optimizations.
-You must uninstall previous build before installing this one.