April, 2014
now browsing by month
I dunno if this against the Community rules since its not LL related (and it just says Discussion in the Title) but…
I tried loads I thought I found the perfect one in “TCM Music Tag Editor” but for some reason there was an update that resized all saved art to 300x300px which IMO is pointless.
Another great one is “MP3Edit” This ones my favourite but the UI could be better and sometimes it won’t read tracks and when it finds art it only displays 4 at a time with no resolution.
Free Paid PC Android whatever all suggestions are welcome or if anyone knows of a decent mp3player app that doesn’t have cover art or has the option to disable it that will do nicely also, cheers lads and lasses.
Mods feel free to delete this if its against the rules, Preferably after I got a few suggestions 😉
]]>Little bug report.
If, for some reason, you set the scale, the position and/or the skew to NaN (for non programmers: Not A Number) the item disappear.
The only way to get it back is to restart the launcher.
With rotation it makes an error.
With size it just apply the minimum possible size (the same as set to zero)
]]>Still have this problem with the buttons at the bottom… Samsung Galaxy S3 on 4.3
Still have this problem with the buttons at the bottom… Samsung Galaxy S3 on 4.3
]]>Apologies if this has been addressed elsewhere. Pointers appreciated.
After last updated from Play Store, “All Apps” shortcut is not recognized.
No templates, updated, Tap “All Apps” ,get “Item is not installed…”.
Tried “Select app”, Tried deleting the shortcut and adding again, Tried “killing the app” and tapping again. Same result. Tapping “App Info” gets me nothing.
My current work around is to associate Tap action with “Search Apps” but that’s not quite the same as having “All Apps.”
Clearly I’m missing something: What am I missing?
Merci D’avance.
]]>Double bug report (don’t be aware of the length of this post :P )
I found this while testing, but researching about it I found the root cause, that is specific. This second bug can be something difficult to achieve, depending how LL is saving this data.
Ok, let’s stop writing abstractly. These are the bugs:
[1] The geometry editor don’t want you to use decimals…if you are Spaniard (some other languages as well)
To be honest I can’t say if this bug was here before…maybe it was since the geometry editor was added!
The bug is simple: the float numbers that you can input in the geometry editor takes ‘.’ dots as the separator between decimals. If your mobile phone is set to a language that use this notation, all is ok.
But if, like Spanish and other languages, you use the ‘,’ comma instead, the geometry editor show the number with the comma, as well as the prompt window…so you need to change it to a dot every time you want to input a new number! Remember that it takes the number with dot, no comma.
Solution? Don’t let the system choose the decimal character, or make the editor to also accept commas.
Note: maybe this happen with other float inputs in other settings as well.
[2] half a pixel? Please no
As the title say, it’s physically impossible to have 1/2 pixel (1/3 , 6/19 , …)
So…why you can set the position of items with decimals?
This is not a silly question, and the answer you can think of is: ‘because you can zoom’
…
Nice try, but no. If an item is at 1.75 it is rounded and placed at 2 even with the biggest zoom. It’s easy to try, just add two identical shortcuts, one placed at ( 0 , 1 ) the other at ( 0.4 , 0.5 ) for example. They will look identical. (Maybe you think this is not very important, it’s only 0.1 more. But remember I’m talking when zoom, and a one pixel line can have the size of the screen, believe me it matters)
So…why? Why don’t just only let the user set it as integers, like with size?
If there is a ‘hidden’ reason, maybe you can alert it when using the .getPositionX/Y … I was crazy trying to figure why my script (will be posted soon) didn’t work with zoom. Then I realized it get fixed just using Math.round( .getPositionX/Y )
(And I have been trying to figure this out since 10.0 version was release. But hey, because of this I found the setPosition(,,,false) bug and this one. Not bad)
Oh, and I also think I know how the .translateIntoScreenCoordX/Y work…because it has also the bug ;)
]]>






D5 Creation