PageProbe - Automatic Page Monitor 的评价
PageProbe - Automatic Page Monitor 作者： Nodetics
Powertop 的评价
评分 5 / 5
来自 Powertop，5 年前Great addon. Works perfectly except for a blip. I seem to be losing log data. Does this addon delete log entries after a specific time period or number of entries?
EDIT: That makes sense for a small number of trackers but I'm dealing with about 5-600 rapidly changing trackers. Any way you could suggest to handle that?
EDIT2: That would be great.
EDIT3: Bug report. You can't open the settings for a monitor beyond the first page. Steps to reproduce. 1: Create enough filters to fill more than a page. 2: Scroll a page below and click settings. 3: Nothing happens.
EDIT4: A batch refresh failed trackers option would be appreciated.
EDIT5: Thank you. Figured it out.
EDIT6: Is the black bar beside the scrollbar in this picture (https://i.imgur.com/1JIIit4.png) intentional? Because it's wasting space.
EDIT: That makes sense for a small number of trackers but I'm dealing with about 5-600 rapidly changing trackers. Any way you could suggest to handle that?
EDIT2: That would be great.
EDIT3: Bug report. You can't open the settings for a monitor beyond the first page. Steps to reproduce. 1: Create enough filters to fill more than a page. 2: Scroll a page below and click settings. 3: Nothing happens.
EDIT4: A batch refresh failed trackers option would be appreciated.
EDIT5: Thank you. Figured it out.
EDIT6: Is the black bar beside the scrollbar in this picture (https://i.imgur.com/1JIIit4.png) intentional? Because it's wasting space.
开发者回应
发布于 5 年前The log has a limit of 200 entries. If there are 200 entries already and a new log entry is registered, the oldest one is deleted. This is necessary because otherwise the log size could grow very large which slows down saving and loading.
EDIT: Fair point. We can make the log size configurable with a warning that having large log size can affect performance.
EDIT3: Good catch. This is fixed in PageProbe 1.11.6+ (available right now). It worked fine on Chrome but Chrome and Firefox seem to produce different element position data for events.
EDIT4: Available in PageProbe 1.16.0+ (right click folder and select 'Refresh Failed Probes')
EDIT: Fair point. We can make the log size configurable with a warning that having large log size can affect performance.
EDIT3: Good catch. This is fixed in PageProbe 1.11.6+ (available right now). It worked fine on Chrome but Chrome and Firefox seem to produce different element position data for events.
EDIT4: Available in PageProbe 1.16.0+ (right click folder and select 'Refresh Failed Probes')