Open astares opened 5 years ago
To limit bug bankruptcy (see https://www.joelonsoftware.com/2012/07/09/software-inventory/) this issue has been automatically marked as stale because it has not had any activity in 6 months. It will be closed in 1 month if no further activity occurs. If this issue remains important to you, please comment to reactivate the issue. Thank you for your contributions.
Joel on SoftwareImagine, for a moment, that you came upon a bread factory for the first time. At first it just looks like a jumble of incomprehensible machinery with a few people buzzing around. As your eyes adjus…
Still relevant
Oops, I didn't see it before. This is an issue of the Settings browser and should be resolved at that level. EpSettings defines:
monitorEnabledSettingOn: aBuilder
<systemsettings>
(aBuilder setting: #monitorEnabled)
label: 'Monitor enabled';
description: 'The Epicea Monitor listens events in the system such as class added and method modified, and records them to the current Epicea log.';
parent: #epicea;
target: self.
We can make this issue less evident by removing it from settings... and report it in general for the settings UI.
I checked in latest P8 and reproduced it.
When you now in the settings browser for the settings of Epica toggle the "Monitor enabled" then the Epicea Dashboard will follow this change and also toggle the "Monitor disabled button".
But this only will work in one direction: if you toggle the Button on the dashboard then the same setting in the browser will not be updated. One has to reopen the settings browser.
I think this is a general updating problem because you already have this effect when opening two settings browsers and toggling a control box.