wrldwzrd89
Member
Try, for example, eating to your maximum fullness (20 in my case) of a 1-full food (I'm using jerky coins), with milk.
What will end up happening is that the GCLI will have roughly 60 messages printed out VERY quickly as KoLmafia detects the consumption results... but the display does not autoscroll to the bottom, as it should when something like this happens, assuming the scroll bar was already at the bottom before this happened (which it was in my case).
EDIT: Just realized that booze works even better for testing this, as mass-drinking 1-drunk boozes prints additional messages about drunkenness gained. Also thought up a simple fix: Before printing anything to the gCLI (for example, because of a request executing), store the gCLI scroll bar position just prior to the print. Perform the print as usual. Then, use the STORED position, not the CURRENT position, to decide whether to autoscroll or not.
What will end up happening is that the GCLI will have roughly 60 messages printed out VERY quickly as KoLmafia detects the consumption results... but the display does not autoscroll to the bottom, as it should when something like this happens, assuming the scroll bar was already at the bottom before this happened (which it was in my case).
EDIT: Just realized that booze works even better for testing this, as mass-drinking 1-drunk boozes prints additional messages about drunkenness gained. Also thought up a simple fix: Before printing anything to the gCLI (for example, because of a request executing), store the gCLI scroll bar position just prior to the print. Perform the print as usual. Then, use the STORED position, not the CURRENT position, to decide whether to autoscroll or not.
Last edited: