I bumped into this when working for a FileView skin: when instructed to [!CommandMeasure ParentMeasure "Update"], the existing position in the item list resulted from scrolling via [!CommandMeasure ParentMeasure "IndexUp"] and [!CommandMeasure ParentMeasure "IndexDown"] is lost, i.e. reset to the very first item in the list.
Normally, this isn't a problem since re-reading the folder is rarely used outside a manual action, but when attempting to periodically monitor a folder for new or changed files (which, as the manual says, can be done only by commanding the parent measure to "Update"), it's extremely annoying to have to re-scroll over and over again to get where you were in the list, only to be undone at the subsequent "Update" commands.
So, I suggest remembering that scrolling position after update commands on the parent measure. I realize why this might be tricky to adjust in the Rainmeter code, as it would involve retaining a position in a list that's technically lost as well (since it's being updated in that very moment), not to mention the possibility that the said position to be invalid depending on the changes potentially operated in the folder, but nevertheless, it would be nice to have. Or, at least a solution to the aforementioned annoyance, one that doesn't involve dynamically setting the values of the Index options (which would make the "Index Up" and "Index Down" commands pointless).
Normally, this isn't a problem since re-reading the folder is rarely used outside a manual action, but when attempting to periodically monitor a folder for new or changed files (which, as the manual says, can be done only by commanding the parent measure to "Update"), it's extremely annoying to have to re-scroll over and over again to get where you were in the list, only to be undone at the subsequent "Update" commands.
So, I suggest remembering that scrolling position after update commands on the parent measure. I realize why this might be tricky to adjust in the Rainmeter code, as it would involve retaining a position in a list that's technically lost as well (since it's being updated in that very moment), not to mention the possibility that the said position to be invalid depending on the changes potentially operated in the folder, but nevertheless, it would be nice to have. Or, at least a solution to the aforementioned annoyance, one that doesn't involve dynamically setting the values of the Index options (which would make the "Index Up" and "Index Down" commands pointless).
Statistics: Posted by Yincognito — Yesterday, 9:50 pm — Replies 1 — Views 55