Lightening launcher panel problem :
Lightening launcher panel problem :
Trying to create the height of a panel. I’m the settings it should be 3 rows high but the visible height of the panel remains as 1 row:(
Suggestions appreciated!
(continued from different screen shots: https://plus.google.com/104271262832831435370/posts/4Tq3nQyRuCq)
And can anyone delete panels? Mine are stubbornly refusing to delete.
« KLLassik for Kustom and Lightning Launcher (Previous Post)
(Next Post) I’m very new to Javascript. »
D5 Creation
As I said: Edit on the PARENT container level and you are able to edit the panel just like any other item.
Lukas Morawietz Ok thanks, that works- screen shots usually help!
As someone new to Lightning Launcher, for consistentcy it would be great if to edit the panel it worked in the same way as selecting any other object for editing like folders, widgets etc. The approach of selecting the parent panel to edit rather than the object in order to edit the object isn’t so intuitive because of the way that other items are selected in order to edit them. I’m sure there’s a good reason for that approach (could be worth mentioning on the text pop up when inserting a panel or on panel edit screen explicitly what is meant).
Having said all that, Lightening is brilliant and I’m using the panels a lot!
The problem is that items like shortcuts, folders, and widgets are real items, something that is there and you can tap, long tap , swipe.
But panels are not items, they are windows to another container that it shown in that space. Tap, long tap and swipe is used in the container, and that is how it should behave.
How could you edit the ‘window’? Going into edit mode in the container that have it.
Maybe you see it unintuitive, but think: could be another way?
Maybe a help will be another option when long tapping the background of the panel to ‘edit parent container’.
I’ll leave this suggestion to Pierre Hébert just in case.
TrianguloY Pierre Herbet it’s looking at this from a user perspective. The inconsistency doesn’t help, even if there is a good reason. One mitigation is to say explicitly in the text box that appears when you add a panel, that you select the desktop to edit/move the panel, for example.
Now that I know, I’m using panels a lot more!
Andrew M Postings the thing is: It is not inconsistent. A panel is like any other item just an item, which means if you want to change its dimensions, you have to edit the parent.
What differs from other items is that it shows a container instead of an icon or text. So, if you click on it the container takes the click. Other items don’t have an own container, so the parent takes the click.
If you get into scripting you’ll notice that there is a panel item and a panel container. Those two differ a lot from each other and you have to get the principle of what an item and what a container is.
What I’m saying is: It might be not be intuitive, but it is consistent. I’d say a hint is the right way to go.
Lukas Morawietz it’s not intuitive nor consistent from the perspective of a person new to it, me. Think personas and user stories or journeys, more the designer’s nor experienced user perspective.
It can be left as it is and I’m sure you can see the likely scenarios. Or at the very least some helpful text.
It would be a shame if the power of Lightening launcher remained for a small number of people; there are some great concepts in LL that a number of people could benefit from.
Have you tired editing the events to get the behavior you want?
Carolyn Boyle I have, that doesn’t work, but thanks. Lukas’s suggestion works.
It doesn’t work if you long press the panel and then edit it (though some of the options look like it should work). Instead, you need to long press on the desktop and in the edit mode you’re now able to change the size of the panel. I’m contrast, for example, if you want to resize a widget, you long press the widget and enter the edit mode that way, rather than long pressing the area around it.
Andrew Manning I’m surprised editing events didn’t work for you. I have long press item event set to “lightning menu” (default is do nothing) and I see no difference in behavior with panels, they behave the same as any other item. And with the new interface it’s easy to access panel properties and container settings from the same mm place. Did you set the long press event to the menu and it didn’t work? And yes, Lukas Morawietz’s point is obviously correct, but the boundary between panel and parent is not always obvious.
Carolyn Boyle thanks for the suggestion. Editing the events didn’t work. But now that I’m long pressing in the desktop and then in edit mode selecting the panel to move or widen it, it’s not an issue (rather than long pressing the panel directly, which didn’t work, even setting the rows to 3 didn’t widen it). Being able to increase the height of a panel from 1 row to 2 or more rows is incredibly handy for the way I work, for example swiping up to move between various music widgets, or to switch from a collection of comms based apps and shortcuts to a set that I use for reading books,mews,more taking etc. Where it really comes into its own is on phablets where I can now reach more options with one hand.
Andrew Manning I understand you said that editing the events didn’t work, my question is did you edit the events exactly the way I did and get a different result? If so, then there’s a bug somewhere. The behavior should be the same on your ad it is on mine. If it’s not then we need to create a bug report.
Specifically, could you try setting the event “long press item” to “lightning menu” ? That’s what I have set and I don’t get the behavior you have described.
Carolyn Boyle have you tried using the events to get the behaviour I’ve described ie panels that are increased in height so for example you can fully see widgets that are 2 or more rows high? And then able to scroll within the panel to see, for example widgets above that?
I can’t recreate that behaviour using events. I can do it by long pressing on the desktop and selecting the panel once in edit more (rather than pressing the panel).
Andrew Manning What we’ve got here is a failure to communicate….
Carolyn Boyle I’m clear in what I’m after:) ie panels that are higher than 1 row eg for putting in widgets that are 2 rows high, with apps etc in the same row, so that you can scroll those two rows down and see a different set of widgets and apps in that panel). Trying the approach that Lukas suggested does exactly that. So I have an approach for what I was trying to do. However, to help LL that could either be made more obvious. Or failing that give the user some information about how to do it. It’s a unique and powerful feature of LL, and one of the key reasons why I use it. It’s a shame if others aren’t aware if that.