{"id":856,"date":"2017-12-12T19:42:15","date_gmt":"2017-12-12T17:42:15","guid":{"rendered":"http:\/\/mattiesworld.gotdns.org\/weblog\/?p=856"},"modified":"2017-12-13T19:31:23","modified_gmt":"2017-12-13T17:31:23","slug":"onscreenclock-v0-5-0","status":"publish","type":"post","link":"https:\/\/mattiesworld.gotdns.org\/weblog\/2017\/12\/12\/onscreenclock-v0-5-0\/","title":{"rendered":"OnScreenClock v0.5.0"},"content":{"rendered":"<h1><\/h1>\n<h1>Customizable colors<\/h1>\n<p>Yes, you read this well! The most requested feature is finally there, although I wouldn&#8217;t call it finished just yet. As of 0.5.0 you can configure the clock and outline color by selecting a color from a predefined palette. You might have noticed I&#8217;m not that savvy with colors (a lot complained about the default green color, or was it yellow? I blame the color blindness) so I wasn&#8217;t sure which colors to include in the preconfigured palette. I found some nice material design style colors but figured people probably don&#8217;t care about material design and would want to tweak the colors anyway. \ud83d\ude42 So I simply configured the colors from a standard 12-color <a href=\"https:\/\/en.wikipedia.org\/wiki\/Color_wheel\">color wheel<\/a>\u00a0and added black and white. The idea is that in a future version, you will be able to select a color from the palette and then tweak it to your liking. At first I didn&#8217;t want to release without the tweaking functionality but since this feature has been delayed for so long, I realized it&#8217;s better to release, put already quite some people out of their eyestrain misery and bear the negative reviews bitching about the fixed palette. \ud83d\ude09<\/p>\n<h1><a href=\"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-content\/uploads\/2017\/12\/color_palette.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-861 size-large\" src=\"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-content\/uploads\/2017\/12\/color_palette-1024x576.png\" alt=\"\" width=\"584\" height=\"329\" srcset=\"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-content\/uploads\/2017\/12\/color_palette-1024x576.png 1024w, https:\/\/mattiesworld.gotdns.org\/weblog\/wp-content\/uploads\/2017\/12\/color_palette-300x169.png 300w, https:\/\/mattiesworld.gotdns.org\/weblog\/wp-content\/uploads\/2017\/12\/color_palette-768x432.png 768w, https:\/\/mattiesworld.gotdns.org\/weblog\/wp-content\/uploads\/2017\/12\/color_palette-500x281.png 500w, https:\/\/mattiesworld.gotdns.org\/weblog\/wp-content\/uploads\/2017\/12\/color_palette.png 1920w\" sizes=\"auto, (max-width: 584px) 100vw, 584px\" \/><\/a><\/h1>\n<p>The reason it took so long is because I wasn&#8217;t sure how to provide a user-friendly user interface for selecting a color on a tv (using a D-pad). I now settled on the fixed palette and found peace with it since I will be offering a fine-tune option later on.<\/p>\n<p>So with the big fancy feature out of the way, what else is new?<\/p>\n<h1>Better gamepad support<\/h1>\n<p>As a <a href=\"https:\/\/en.wikipedia.org\/wiki\/Nexus_Player\">Nexus Player<\/a> user, I was harassed by <a href=\"https:\/\/issuetracker.google.com\/issues\/69320537\">this nasty bug<\/a> Google rolled out a few weeks ago which causes the remote to go to sleep at the worst possible moments, i.e. when you&#8217;re using it. \ud83d\ude09 It&#8217;s really frustrating when you&#8217;re trying to watch tv, but it&#8217;s even more frustrating when you&#8217;re developing an app. \ud83d\ude09 I tried using an emulator but my pc hardware is officially unsupported now by google&#8217;s emulator (missing some instructions). It&#8217;s time to replace this 8 year old rig, it served me well.. Anyway, I&#8217;m digressing.<\/p>\n<p>As a replacement for the bluetooth LE remote, I started using a Logitech gamepad. Unfortunately, it turned out to not emit DPAD_CENTER events required for adjusting size and position. From now on, gamepads should work just as well (use the &#8220;A&#8221; button to press &#8220;enter&#8221;).<\/p>\n<h1>Positioning the clock<\/h1>\n<p>While I was at it, I added a notice about keeping the button pressed to reposition the clock faster. It seems some people have trouble moving the clock around and complain having to move it a pixel at a time. The input dialogs for repositioning and scaling the clock were originally stubs for a nicer UI but as a lot of things, it just stayed.. Might improve in some future version.<\/p>\n<h1>Android 4.0.3+ required<\/h1>\n<p>The original plan was to have the clock run on as many devices as possible (also smart phones). So for a long time, the min api level was 10 (Gingerbread or 2.3.3+). I remember having a gingerbread device and often being annoyed by developers bumping the android version too early, effectively abandoning me from a functioning app (due to backend changes). I looked at the app stats and it turns out there are only 3 users below 4.0.3. I apologize, but no new version anymore for them. The bump is due to support lib requirements.<\/p>\n<p>&nbsp;<\/p>\n<h1>Changelog<\/h1>\n<pre>+ customize clock and outline color\r\n* fix pressing buttons with gamepad\r\n* size and position pref: hint about keeping the button pressed to go faster\r\n* min api level bumped from 10 to 15 (4.0.3) due to support lib requirement\r\n* renamed main activity title because Oreo shows it in the launcher<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>Customizable colors Yes, you read this well! The most requested feature is finally there, although I wouldn&#8217;t call it finished just yet. As of 0.5.0 you can configure the clock and outline color by selecting a color from a predefined palette. You might have noticed I&#8217;m not that savvy with colors (a lot complained about &hellip; <a href=\"https:\/\/mattiesworld.gotdns.org\/weblog\/2017\/12\/12\/onscreenclock-v0-5-0\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">OnScreenClock v0.5.0<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35,40],"tags":[],"class_list":["post-856","post","type-post","status-publish","format-standard","hentry","category-android","category-onscreenclock"],"_links":{"self":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/856","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/comments?post=856"}],"version-history":[{"count":10,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/856\/revisions"}],"predecessor-version":[{"id":867,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/856\/revisions\/867"}],"wp:attachment":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/media?parent=856"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/categories?post=856"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/tags?post=856"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}