Re: Introducing CherryPicking - new Windows & Linux Pool Hopper
let me think of some other features... 
OK OK I got one...
When updating the pools...the stuff flies by too fast for my 40 year old eyes...The reason it scrolls by so fast is because you have verry little information per line.
Actually I was already planning to do that, I had noticed that the update spam didn't really allow you to see much info.OK OK I got one...
When updating the pools...the stuff flies by too fast for my 40 year old eyes...The reason it scrolls by so fast is because you have verry little information per line.
That is the only thing about the hopper that I think "can be improved", meaning I think everything else is perfect!
I'm really happy to hear you think CherryPicking is that good! 
Bloodred a pair of suggestions.
First the latest version is solid.
Two minor UI tweaks.
1) eliminate need for pressing enter. i.e. e to exit not e+enter. i for info not i+enter.
I believe it would be as simple as replacing readline() w/ getchar(). Java isn't my language but most languages support both single char reads and line reads from console.
2) Include the "i" info screen when you exit. i.e. hitting e displays final info (simply a call to the function which handles i and then exits. Often I do this manually (i + enter, e + enter) but would be nice to have it all wrapped up.
1) This is actually pretty much impossible in a Java "console" application. Java console apps only really have an input and an output stream, they are not actually aware of running in a console or not and they don't care. Basically, the JVM actually handles the console stuff and reads the application's output stream and writes to its input stream. This means you cannot intercept keypresses or anything like that since you only have access to what the virtual machine is giving you, even if I change to a simple read() that returns a single char, it still only gets written to the input stream itself after you press Enter.First the latest version is solid.
Two minor UI tweaks.
1) eliminate need for pressing enter. i.e. e to exit not e+enter. i for info not i+enter.
I believe it would be as simple as replacing readline() w/ getchar(). Java isn't my language but most languages support both single char reads and line reads from console.
2) Include the "i" info screen when you exit. i.e. hitting e displays final info (simply a call to the function which handles i and then exits. Often I do this manually (i + enter, e + enter) but would be nice to have it all wrapped up.
I haven't done too much research into this topic, there may be some way to get around this. Native code could be used, but that would likely cause issues with cross-platform compatibility.
Not saying that I'm 100% sure it's impossible, but don't expect this.
2) Sure, this is no problem and will be there in the next update.