Lutz Linke
now browsing by tag
Item style stays “focus” after gesture action was performed.
Well, mainly I have a shortcut with swipe gesture to unlock lockscreen. Works, but next time lockscreen is shown, the item is still focused.
]]>“Copy style” also copies gesture settings… why?
Copied style to a “do nothing” shortcut with gestures, all overwritten and lost.
I think gestures are actions/behavior, not style! It’s like copying a shortcut’s action. This should definitely be changed.
]]>Would it be possible to “import” a template instead of applying it?
Currently when applying a template, the current desktop is deleted and replaced. By importing a template I mean new desktops should be added and the termplate applied to those.
Example: With the new lockscreen feature I can imagine great templates coming up for that. When exporting, it’s possible to choose which desktops to export. So it’d be possible to only export the lockscreen desktop. If this could be imported as new desktop, it could be used by anyone independent from the homescreen.
Also, it’d be possible to try out others’ creations without loosing one’s own current setup.
]]>Lockscreen after a while always reverts to default Android lockscreen.
Nexus 4 with Android 4.4 KitKat by the way.
After setting a desktop as lockscreen in LLx 9.2, I can lock my phone and unlock using the LL lockscreen. But after a while, when I switch on the phone, the default Android lock (that ring-thing) is active again. From this moment on, LL lockscreen does not become active again, until I enter LL settings and once again choose the lockscreen desktop.
According to the statement “in order to use the lock screen with this version, set android security setting to screen lock = swipe” I did so. No PIN or gesture unlock, and certainly not “none”.
Is this a bug, or am I just doing something wrong?
I have “Keep Lightning running” enabled and “Minimize memory usage” disabled. Just in case this might interfer.
]]>Some thoughts on inheritance for Pierre Hébert
Requirements:
– adding inheritance feature should not break existing desktops/templates
– inheritance however should be active as default for new panels/folders
– settings for items and folder should be inherited from desktop to panels and folders; or generally: from the container a panel/folder is placed within
What to inherit:
– *”Items”*:
Settings for Text, Icon, Pos., Box; not sure about “+”
– “Icon Pack”:
I think one should be able to apply an icon pack at desktop level and ALL icons in panels and folders should use the same icon pack.
– “Folder windows”:
Note: Currently these settings can only be set at desktop level, but NOT when customizing a panel or folder.
When adding a folder to a panel, it seems at that moment some (i.e border colors, position; but NOT background color or item settings) current desktop settings are copied, but when changing those at desktop (manually or by loading a style), they are not updated.
This in consequence means, each folder within a folder must later on be configured separately by opening the folder and then changing it’s settings (however, strangely the “Current Folder Window” settings have a “Custom” checkbox in front; but currently the parent settings are nowhere editable).
Suggestions:
An option “Inherit from container” or “Inherit from parent” should be added. When this is enabled, all inherited settings must have the “custom” checkbox. When “inherit” is not enabled, the “custom” checkbox should not be there.
Where to add this option to? To granually define inheritance, it could be added as first option in i.e. “Items” in each tab “Text”, “Icon”, etc. But personally I think one option per panel or folder in the category “Miscellaneous” whould be the sufficient.
What to do, when inheritance is enabled if it was disabled? This is mainly important for “updating” existing setups after inheritance feature is available. I think a confirmation “Keep current settings?” (or inverse “Update current settings?” or “Apply parent settings?”) should pop up.
]]>Here are some translation issues I found.
– “Preferences”: please change back to “Customize Lightning” or “Lightning settings”
– “Customize…”: should be changed to “Customize Item” or “Item settings”
– “Folder options”: should be “Customize Folder” or “Folder settings” (homogenize wording for Lightning/Desktop/Folder/Panel)
– Title in Panel and Folder settings: currently in folder’s and panel’s settings the title says “Customize Lightning”, this should be specific to what one is currently customizing
– Miscellaneous descrption: no description text in panel’s settings, wrong text (applies to desktop, not folder) in folder’s settings
Generally:
– Wording should be homogenized, using same words (like Customize Lightning/Desktop/Panel/Folder).
– If “Customize Panel/Folder/etc” is used, I think the name of the target (Item/Folder, Panel) should be capitalized to strengthen the meaning.
– Trailing “…” is not used consistently. In most cases it means like “another choice dialog is following”, but not in all cases.





In 9.1b1 (maybe others, too), when restoring a backup, widgets are not created.
Using G+ web page and app I just a came up with a (maybe crazy) feature sugestion regarding scrolling.
1.) Unidirectional scrolling
We can currently pin items, even just horizontally or vertically. What about in addition restrict vertical/horizontal scrolling to only one direction from it’s original position.
The effect I have in mind: scroll down on a G+ page, the menu bar raises up to a certain point, then stops.
2.) Parallax scrolling
Best explained with example first: open any user’s profile in the G+ app. Scroll down. The page moves up, but the background behind the profile picture moves at a different speed.
What I have in mind for LL: in the “+” customization i.e. for a panel there could be a “scrolling factor”.
50%: scrolling the desktop a complete page would only scroll the panel half a screen. Vice versa 200% would move the panel twice the way the screen does.
Pierre Hébert , do you generally think this might be possible to implement?
]]>Would it be possible to only “partially apply” APK-templates?
I mean: I soon publish an update of my template. Mostly I added many new styles (read: “Desktop Settings”), added on requests some new folders and only a liiitle bit changed the layout.
But: If users download the update, they need to reapply it, right? But if they do… i.e. all their sorted apps in folders, their own widgets are lost.
Another idea: The styles i my template are saved as “desktop settings”, containing ALL settings. How about “themes” that contain only a subset of the desktop settings (delta) like colors etc?
]]>
D5 Creation