Pierre Hébert its feature suggestion time!
Pierre Hébert its feature suggestion time!
1) Add a ‘class’ option for items
2) Add the ability to use CSS to style items by class, ID, Name, or label
This would allow for changing styles quickly for multiple items all at once without changing all items in a container
Say you have a list of items separated into categories and have items as labels. This would allow adjusting all of the labels at once without using “Copy style” for each label
]]>(Next Post) Last update not setting very well with my Note 4. »
D5 Creation
< ![CDATA[
I fear CSS… Don’t know why, but each time I have to touch CSS it always become a nightmare, lol.
Well, that would be great though, but at the moment I dont’t wish to implement this, under the hood this is quite complex to implement. I would prefer to implement this another way. Maybe through some sort of simpler tagging and multi selection.
]]>
< ![CDATA[
Oh it’s time?
Here are mine:
3. Get the whole image of any item (e.g. shortcut: label and icon and background, panel: the current visible stuff inside,… )
4. Get the view object of any item.
5. More pointers in motion event
6. Setting any item parameters non-persistent
7. Script access to general settings
8. (more) events in App drawer
I think most of these were already mentioned, I’m just concluding.
]]>
< ![CDATA[
I think you know it is always time 😉
3) and 4) can be handled by the same method (item 173 in the TODO list)
5) the event is the one given by the Android framework, so if there are only two pointers, then it means that the device only supports 2 🙁
6) that’s not really possible I think, or it would need to make a copy of the existing configuration first
7) item 170 🙂
8) item 175, but which event would you like to see the most ?
]]>
< ![CDATA[
8. Tap empty space, swipes and as always, position changed, which is in my opinion the best event of all time 🙂
]]>
< ![CDATA[
How about adding a class and rather than having CSS..
2.5) All of the items with the same class have a linked style..
So if you change style on one item it changes on the rest at the same time
No more CSS 😛
]]>
< ![CDATA[
5. I’ve tested now. My device definitely supports up to five fingers, but in LL the event gets aborted as soon as the second finger goes down.
]]>
< ![CDATA[
Is it possible that LL consumes an event with more than one finger for its own two-finger gestures?
]]>
< ![CDATA[
Ren Shore I am wondering: would “CSS like” properties be used for batch customization, or for other purpose ?
Lukas Morawietz this might be the case. I just tested it myself and I confirm that I only see 2 pointers
]]>
< ![CDATA[
I can confirm that swiping with two fingers above an item with the touch event (the two fingers in the item, a big one) launch the event associated with that gesture, instead of be passed to the item.
]]>
< ![CDATA[
Pierre Hébert I think having a class and linking all of the items with the same class would likely be a much better idea than implementing full CSS.. just have
]]>
< ![CDATA[
That’s described much better.. Not necessarily having a stylesheet but having a class option and having items with the same class changing style at the same time
]]>
< ![CDATA[
Yes to batch editing
]]>