John Torjo
John Torjo
they are of course quite CPU intensive. And when I'm moving a lot with the arrows, need to find a way to speed things up - eventually don't update the...
- allow extending selection up/down - by a period (in lines, and/or times) - can have things such as "50" (50 lines up/down), "+20 -10" (20 down , 10 up),...
``` // possible optimization: // if the new quick filter is a subset of the former filter, I should run it only on the former sorted_line_indexes ```
Run it with Parallel.for (and sort line_indexes in the end) Test on event log (search for .net runtime)
right now, it's only kept in the log. I should hold it in the context as well, so that I can reuse it across the same type of logs.
this should pretty much show logs related to the existing log. For instance, say the log is called "MyApp.log" If there are logs like "MyApp.24-19-2016.log", or like "MyApp.log.1" and such,...
-> like, for instance ctx1 + ctx2 + ctx3 and show them one behind another, and allow making the row bigger, so that I can have a row allow several...
For instance, event viewer. It's very likely because the selection index is reversed
1. When opening a log, and we're showing/hiding columns -> this is seen visually (as if, most columns are hidden, and then some are re-shown). I should be able to...
... so that I could treat a column as "int", and allow > and < Or, same thing for a date/time column.