(This seems like a bug, but it is a feature suggestion)

The ‘bounding box’ of a container is not recalculated when moving items from script.

If you move an item from script ‘outside’ of the available pages, you won’t be able to scroll to it until the launcher refresh (open another app, then go back to the launcher). This is more noticeable if you have the ‘fit desktop to items’ active.

This means that the ‘computation’ of the available screen is made from time to time, I guess when the container loads, when you exit edit mode… But not when moving items from script.

Will be possible to add a container.refresh() or similar to manually force this calculation? Is it too cheap to do it every time an item moves (I guess not)?

Or

Is it possible with something currently available?

I found that calling {LL.save();container.getProperties().edit().commit(); } works. But it takes almost a second to refresh the container. ( [!] Something to note: if you don’t call LL.save() before the commit() all the container returns to the previous state. I guess this is the reported and known issue of deleted items that appears again and related)

Second suggestion:

Could be possible to set ‘borders’ in the calculation of the bounding box when the ‘fit desktop to items’ is checked? I mean to add an offset so that you can always scroll a little more than the last item.

I’m suggesting this mainly because I have transparent nav bar, and the items scroll under it. But now the last item is always under the bar, so I can’t click it. I need to manually add an item at the bottom to force it to scroll a bit more.

I know I can automate this from an script, adding automatically an invisible item accordingly. But it seems like a ‘bad’ solution in my opinion. A built in feature will be better.

]]>

In v10.5b1 there was a specific feature added: “when creating shortcut to scripts, optional data can now be passed as argument” that has gone unnoticed, and it’s more powerful than it seems. (Mainly because I think almost nobody used it in their scripts)

With this, a script can have custom parameter per item that don’t need to be stored in a tag, or included in the code as config.

However, now that I discovered it and I want to use this feature, it is still hard to use: you can only use it from ‘launch a shortcut, lightning, run script’, if you use the normal ‘run script’ that dialog is not showed [Even thought it is possible: you can set it as a custom EventHandler from a script]

There is another old suggestion: when choosing a script to run, show only the list of scripts, not the whole script editor.

So, Pierre Hébert, my suggestion is:

How difficult will be to have a custom dialog with:

Title: “Choose a script”

Drop down list with the list of scripts (the same one as in the script editor)

The ‘extra data passed, leave blank if not used’ text

A text box where to add the extra data

(Optionally: a checkbox to show/hide that two last items)

A cancel button and a accept button.

This will improve the mentioned feature, and people will understand better how to choose a script (pressing back to accept is, sorry, not obvious :/ )

Note: I know you said you will be busy, but I hope you can add this to the to-do list 🙂 (and I hope this is easy enough to do it at once, but I don’t know)

]]>