v10.7b6
v10.7b6
An iteration over the previous beta, with many minor fixes, improvements or refinements.
This time the app drawer has received quite a few changes, especially a new “batch add” mode. Let’s see how it goes.
And there’s a new default setup. For those adventurous enough to backup and clear their app’s data, I would be glad to hear your opinion 🙂
The next version will be either the release, or another beta if bug fixes need it, but I don’t plan to add any new feature in this round. I would like to freeze the current version for the release. Only one thing is missing in this update before the release: the icon.
Enjoy!
]]>
D5 Creation
< ![CDATA[
Pierre Hébert, you forgot to add the publishing date in the change log page
]]>
< ![CDATA[
After first time going into settings, my status bar turned red on home desktop. (fresh install)
]]>
< ![CDATA[
Sounds great, will try.
]]>
< ![CDATA[
Did you improve speed? Feels quite faster everywhere.
]]>
< ![CDATA[
Horizontal scrolling in the app drawer 😀
]]>
< ![CDATA[
Lukas Morawietz , yes I wanted the status bar to be consistent with other screens (same with navigation bar). It should now be red in the first desktop and in the app drawer after a fresh install.
Lutz Linke yes!!! there are two speed optimizations. I didn’t want to mention them because this is often subjective and I was hoping spontaneous and unbiased feedback on these speedups 🙂
]]>
< ![CDATA[
Pierre Hébert it turned red when I opened the settings. It wasn’t before.
]]>
< ![CDATA[
Cleared data, im liking the default setup 👍
]]>
< ![CDATA[
This must be the time for pixels to heat, they don’t become red before to be really hot 😉
More seriously: I will have a look at this, couldn’t reproduce it yet but I don’t think this is device specific 🙁
]]>
< ![CDATA[
Yano that new menu the one with the red background, how do i change it’s color, or did I find a bug. I set it black it goes black but then when i swipe up its red again.
]]>
< ![CDATA[
What happened to all the icon config settings? Mask, overlay, etc…
]]>
< ![CDATA[
There still there just checked, you disabled beginner mode?
]]>
< ![CDATA[
Jay M duh /head slap/ 😉 I haven’t cleared data to check defaults in soooo long.
]]>
< ![CDATA[
Next thing is to modify is the welcome message so that it includes some kind of “expert mode” checkbox! (and other things)
]]>
< ![CDATA[
I even purposefully did a fresh install to read the tips and hints and STILL… :-/
]]>
< ![CDATA[
Pierre Hébert It IS very noticeable! Companion’s animations are just flying, have to slow them down 😄
But honestly: what did you improve? It’s great!
(…memory usage also improved?)
]]>
< ![CDATA[
That’s very simple: the app skips rendering of items out of view. It used to be done by the android framework through clipping, but for some reason it doesn’t work anymore this way now. So I implemented it myself.
No memory usage optimisation although this could be an unexpected side effect: less work also means less memory used (during a short time at least).
]]>
< ![CDATA[
Pierre Hébert Then it’s clear why Companion benefits so much from the optimization. Zoom out and you see how much is really out of view. Awesome!
But wasn’t it there before, also? When opening my left sidebar I can clearly see icons popping up column after column as they come into view (also with 10.6).
]]>
< ![CDATA[
Bump
Yano that new menu the one with the red background, how do i change it’s color, or did I find a bug. I set it black it goes black but then when i swipe up its red again.
Is this happening for anyone else?
]]>
< ![CDATA[
Lutz Linke the “popping effect” you see is due to the “minimize ram usage” option: it will load icons on demand and asynchronously when the item need to be displayed. That should be visible only once.
Jay M confirmed ! The customization is lost 🙁
]]>
< ![CDATA[
Wow, super. I missed the store’s “llx updated” message, somehow but i felt it immediately. Wow.
Only wen i saw my page-indicator changed i looked and saw the version change.
Keep up the good work!
]]>
< ![CDATA[
The default setup is really nice. And the explanation pop-up are nicely done.
]]>
< ![CDATA[
Thanks 🙂
]]>
< ![CDATA[
Trying the new default setup now:
LOL 1 @ the double page-indicator
LOL 2 @ the script-editor icon < -- it's a bug
Overall: nice job.
]]>
< ![CDATA[
Jappie Toutenhoofd LOL, yes icon of Script Editor is a “bug”… literally.
]]>
< ![CDATA[
Cool I think I found another bug.
]]>
< ![CDATA[
Lol, when I saw this “bug” icon, I immediately thought it was perfect for the script editor 🙂
Although, agreed, it is more suited for some kind of debugger or bug report.
]]>
< ![CDATA[
Hi! When I select “Script…” in the item context menu nothing happens.
How can I see all scripts in the new default theme?
]]>
< ![CDATA[
Vlad K. it probably means that there is no script with the “item” flag to show ? From the script editor you can toggle flags to make scripts appears in menus or not.
]]>
< ![CDATA[
Pierre Hébert On the original script editor you were able to view what script were being used, ie long press panel – Panel settings – Events & actions – Position changed – Run a script and the script assigned to that panel would open. Any chance the new script editor will work the same way? With this function there would be less chance assigning the wrong scripts to items.
]]>
< ![CDATA[
Yes, this selection process will be improved (but not for the next release). The current one is a “transitional” one.
]]>
< ![CDATA[
Pierre Hébert I’ve been using this slide panel script for months now without any issues but when I try to assign it to a new layout since the beta update nothing happens, I don’t even get an error message.
var name= “parallax” //the label of the item
var amount = 0.5 //the parallax effect, between 0,1
var cont=LL.getEvent().getContainer();
var it=cont.getItemByLabel(‘apanel’);
it.setPosition(cont.getPositionX()* amount+it.getWidth()* (amount +1.5),0);
]]>
< ![CDATA[
There is an issue in the current build but there is a workaround: when selecting the script hit back instead of ok in the script data dialog.
]]>
< ![CDATA[
Thanks, that did the trick.
]]>
< ![CDATA[
Great! (will be fixed in release)
]]>