btolson
06-09-2012, 10:44 AM
First, brief definition of terms since I don't know the official ones:
-a "popped out" hotbar is a hotbar that has been extracted from the main hotbar and is now taking up its own individual screen real estate
-a "popped in" hotbar is a hotbar that has been inserted into the main hotbar, and is hidden from view unless you seek to it via the main hotbar's arrows or CTRL+mouse_wheel
Now for the actual issue, the new /ui load layout [filename] command is unable to do at least 2 things, preventing it from correctly applying a saved layout without some help:
1) it cannot "pop out" or "pop in" hotbars from the main hot bar
2) it cannot change the vertical/horizontal orientation of a hotbar
hypothetical example:
- create a layout that includes hotbar 13 "popped out", and in a vertical orientation
- save this layout
- change hotbar 13 so it is "popped in"
- load the layout, and take notice as hotbar 13 is still "popped in" and cannot be seen
- change hotbar 13 so it is "popped out", vertical, and in a random location on screen
- load the layout, and take notice as hotbar 13 is now in its correct, previously saved location
- change hotbar 13 so it is in a horizontal orientation and in an arbitrary position
- load the layout, and take notice as hotbar 13 is unmoved and still horizontal
- change hotbar 13 so it is in a vertical orientation, and in a random location on screen
- load the layout, and take notice as hotbar 13 is now in its correct, previously saved location
This certainly seems like a bug to me, though it has an easy workaround: if a hotbar doesn't go where it's supposed to when you load a layout, manually change that hotbar's vertical/horizontal setting or pop it out/in if necessary, and then load the layout again to set its proper position.
Additionally, I intermittently get a <string table error; tableDID run into when trying to load a layout. This seems to happen the most when trying to load a layout many times in a brief span of time (such as when trying to workaround the above issues). Doing this also seems to incrementally ramp up memory usage.
Beyond these issues, the new ui load feature seems to work flawlessly, and is a real godsend - thanks for implementing this!
-a "popped out" hotbar is a hotbar that has been extracted from the main hotbar and is now taking up its own individual screen real estate
-a "popped in" hotbar is a hotbar that has been inserted into the main hotbar, and is hidden from view unless you seek to it via the main hotbar's arrows or CTRL+mouse_wheel
Now for the actual issue, the new /ui load layout [filename] command is unable to do at least 2 things, preventing it from correctly applying a saved layout without some help:
1) it cannot "pop out" or "pop in" hotbars from the main hot bar
2) it cannot change the vertical/horizontal orientation of a hotbar
hypothetical example:
- create a layout that includes hotbar 13 "popped out", and in a vertical orientation
- save this layout
- change hotbar 13 so it is "popped in"
- load the layout, and take notice as hotbar 13 is still "popped in" and cannot be seen
- change hotbar 13 so it is "popped out", vertical, and in a random location on screen
- load the layout, and take notice as hotbar 13 is now in its correct, previously saved location
- change hotbar 13 so it is in a horizontal orientation and in an arbitrary position
- load the layout, and take notice as hotbar 13 is unmoved and still horizontal
- change hotbar 13 so it is in a vertical orientation, and in a random location on screen
- load the layout, and take notice as hotbar 13 is now in its correct, previously saved location
This certainly seems like a bug to me, though it has an easy workaround: if a hotbar doesn't go where it's supposed to when you load a layout, manually change that hotbar's vertical/horizontal setting or pop it out/in if necessary, and then load the layout again to set its proper position.
Additionally, I intermittently get a <string table error; tableDID run into when trying to load a layout. This seems to happen the most when trying to load a layout many times in a brief span of time (such as when trying to workaround the above issues). Doing this also seems to incrementally ramp up memory usage.
Beyond these issues, the new ui load feature seems to work flawlessly, and is a real godsend - thanks for implementing this!