Console: scroll down should end with an empty line
Laosh'Ra
Join Date: 2011-12-09 Member: 137232Members
<div class="IPBDescription">because erasing the last command manually can take a bit</div>i guess this is standard practise e.g. in linux bash. to clarify what i am talking about:
say i just entered some commands:
r_atmospherics 0
r_shadows 0
r_bloom 0
but i got distracted for some reason and now i'm not sure wether i forgot any of these. i look it up by using the up- and down arrow keys to cycle through the history of recently entered commands. no command was missing so i'm happy. but now i remember i also want to use a new command, i_rawinput.
now i have to erase the entire command line pressing backspace. i can keep it pressed but it still takes a while. it is much more handy to get an empty line just by scrolling all the way down (at r_bloom 0, i press down once more to end up with an empty line. i could go back to r_bloom by pressing up again).
you might think this is a very minor issue. and i guess you are right :) i would not suggest this if i was not convinced that it is quite easy to implement this change. granted: you can just confirm the selected command (which might cause some problems depending on the command) or you simply re-open the console, both methods clear the command line. still, not everyone will think of this and it seems a bit annoying.
say i just entered some commands:
r_atmospherics 0
r_shadows 0
r_bloom 0
but i got distracted for some reason and now i'm not sure wether i forgot any of these. i look it up by using the up- and down arrow keys to cycle through the history of recently entered commands. no command was missing so i'm happy. but now i remember i also want to use a new command, i_rawinput.
now i have to erase the entire command line pressing backspace. i can keep it pressed but it still takes a while. it is much more handy to get an empty line just by scrolling all the way down (at r_bloom 0, i press down once more to end up with an empty line. i could go back to r_bloom by pressing up again).
you might think this is a very minor issue. and i guess you are right :) i would not suggest this if i was not convinced that it is quite easy to implement this change. granted: you can just confirm the selected command (which might cause some problems depending on the command) or you simply re-open the console, both methods clear the command line. still, not everyone will think of this and it seems a bit annoying.