So yesterday i was without Internet which suuuuuucked :( but it give me time to rework my TV setup.
So yesterday i was without Internet which suuuuuucked 🙁 but it give me time to rework my TV setup. Its still not finished but im loving it so far there’s just a couple things i cant figure out im using the latest version of LL.
#1. The clock, the date and the title all get focused when navigating with my remote i can set them to be not clickable but i dont see a way to stop them being focused. They dont do anything nothings mapped to them so i dont need them to be selectable.
#2. On the clock theres a white square (holds the seconds) i have 2 actions mapped to it on tap it zooms full scale and onlong tap it restarts the app/launcher these actions are just used to demonstrate whats happening. As you can see when the launchers restarted my setup shrinks (zoom 100p i think its called) this also happens if i press the back button or the escape key on a keyboard. I exported the setup to my phone and tested it there but it does the same thing.
#3. Is it possible to set the focus to always be on the Live TV tile because obviously thats going to be the most used.
The tiles that say stuff like “wifi info here” are just place holders im gunna replace them with some cool custom views 🙂 Feedback welcome 👍
]]>
D5 Creation
< ![CDATA[
To prevent some items to be focused, try this
some_item.getRootView().setFocusable(false);
I really don’t know whether it will work or not.
When the app starts, it always display the desktop at the (0,0) position with a 1 scale (unlike the app drawer). The current position and scale are not saved, originally it was for safety reasons I am not sure it still needed yet.
For #3 you may also try some_item.getRootView().requestFocusFromTouch()
]]>
< ![CDATA[
Pretty sweet though. I like it
]]>
< ![CDATA[
I’m thinking that if it zooms out to 100 percent, then you are using it zoomed in at some level.
Why not make it big enough so that 100% is full screen?
Something with the t.v. resolution? …or?
]]>
< ![CDATA[
Cheers il give it a try when i get home, fingers crossed 🙂
]]>
< ![CDATA[
Chris was right my setup didnt match the screen res. I was using grid lines to help me position stuff and i must of resized things to match one of the grid lines instead of the page border and probably made it worse when i changed the grid size to 30 x 20. So thats problem #2 solved. I have no idea how/where to use that focus script^ though for #1 and #3.
]]>
< ![CDATA[
The setFocusable script could be run from the item resume event.
The requestFocus one should be called at startup, but maybe not exactly at startup and with a small delay, maybe 500ms. Try this in the load event:
setTimeout(function() {
some_item.getRootView().requestFocusFromTouch();
}, 500);
]]>
< ![CDATA[
Cooool the setFoucusable script works great 🙂 i cant get the other one to work though but if the other one works this one probably does 2 am i using it wrong?
in the desktop load event i have this script set to run
var d = LL.getDesktopByName(“Home”);
var item = d.getItemByName(“weather”);
item.getRootView().setFocusable(false);
]]>
< ![CDATA[
If this script works for one item, I don’t know why it wouldn’t work for any other one. Could it be that the view is recreated in the meantime and the script has to be run again (item modified)?
]]>
< ![CDATA[
Its just a text item nothing special, im buzzing the setFocusable script works though 🙂 i can do without the other 1.
]]>
< ![CDATA[
Just noticed ive been saying the setFocusable script works its actually the requestFocusFromTouch script that works (#3) my bad i got mixed up because of how i named the scripts in the Editor.
]]>