https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #11 from TallFurryMan ---
Sorry I meant the full path to the logs folder.
>From memory that is ".local/kstars/logs" or something? "logs" doesn't exist by
default.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #10 from Jasem Mutlaq ---
I thought .local is standard, even in non-KDE environments.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #9 from TallFurryMan ---
Yes, true, they are merged into the main log.
I probably missed a configuration change as I was used to look for them on the
server. I remember the checkbox on the INDI panel, and it's probably not
checked.
My remar
https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #8 from Jasem Mutlaq ---
INDI logs are not related to KStars, they are created by INDI server and
drivers.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #7 from TallFurryMan ---
I think there's a possible regression on log record.
On one hand folders supposed to contain logs are NOT created automatically.
When creating them manually, logs start to record when launching the
application.
Howev
https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #6 from Jasem Mutlaq ---
Yes it's the same file (if you choose file logging) but now all categories and
their logging levels (info, warn, debug..etc) is controllable at run time and
via environment variables, in addition to KStars control vi
https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #5 from TallFurryMan ---
This is excellent. I didn't understand where the logs would end up from the
patch (my guess is that they are still at the same place), so I need to read
documentation about the Qt logging framework. I assume adding a
https://bugs.kde.org/show_bug.cgi?id=383177
Jasem Mutlaq changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #3 from Jasem Mutlaq ---
I understand. Actually, KStars should be using Qt Logging Framework. The
logging stuff was added before the Qt Logging Framework become mature. I will
take a look at that again.
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #2 from TallFurryMan ---
Yes, logs can be generated by KStars, Ekos and INDI (when the .indi/logs folder
exists!), but the only relation with the current observation plan is the name
of the target and index of the scheduler job. The log does
https://bugs.kde.org/show_bug.cgi?id=383177
--- Comment #1 from Jasem Mutlaq ---
Isn't this already implemented? Go to KStars --> Configure --> Advanced and
configure logs for Ekos. There are no control over INDI logs since these are
generated by INDI.
--
You are receiving this mail because:
Yo
11 matches
Mail list logo
