Notice: A non well formed numeric value encountered in /home/www/lightninglauncher.com/docs/www/flyspray/includes/class.flyspray.php on line 96 Notice: A non well formed numeric value encountered in /home/www/lightninglauncher.com/docs/www/flyspray/includes/class.flyspray.php on line 96 Notice: A non well formed numeric value encountered in /home/www/lightninglauncher.com/docs/www/flyspray/includes/class.flyspray.php on line 96 Deprecated: Function create_function() is deprecated in /home/www/lightninglauncher.com/docs/www/flyspray/includes/class.flyspray.php on line 104 Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/www/lightninglauncher.com/docs/www/flyspray/adodb/adodb.inc.php on line 845 Deprecated: Function create_function() is deprecated in /home/www/lightninglauncher.com/docs/www/flyspray/includes/class.user.php on line 111 FS#69 : Update container bounds dynamically

Lightning Launcher

Notice: Undefined index: tasklist_type in /home/www/lightninglauncher.com/docs/www/flyspray/includes/class.tpl.php(128) : eval()'d code on line 85 Notice: Undefined index: tasklist_type in /home/www/lightninglauncher.com/docs/www/flyspray/includes/class.tpl.php(128) : eval()'d code on line 90
  • Status Closed
  • Percent Complete
    100%
  • Task Type Enhancement
  • Category Navigation
  • Assigned To Pierre Hébert (pierrox)
  • Operating System Android
  • Severity Low
  • Priority Normal
  • Reported Version 12.7b6
  • Due in Version 12.8
  • Due Date Undecided
  • Votes 0
  • Private No
Attached to Project: Lightning Launcher
Opened by TrianguloY (TrianguloY) - 2015-11-29
Last edited by Pierre Hébert (pierrox) - 2015-12-11

FS#69 - Update container bounds dynamically

Example: in a container you have items on first and second page. You can scroll to first and second page only. If you move the items by script to the third page, you can't still scroll to the third page and you need to close the launcher and wait until it updates itself somehow.

Possible fixs:

Fix #1: add a container.updateBounds();

Fix #2: add a container.setBoundingBox(..) allowing the user to set a custom bounding box. (With a way to detect the default one)

Fix #3: update the bounds automatically when an item is moved.

This task does not depend on any other tasks.

Closed by  Pierre Hébert (pierrox)
Friday, 11 December 2015, 09:51 GMT
Reason for closing:  Implemented
Additional comments about closing:  #1 and #2 done. Not #3 in order to keep things efficient when updating many items

Loading...