Opened 16 years ago
Last modified 4 years ago
#3362 assigned bug
[InstallerCD] Artifacts after leaving KDL (easy)
Reported by: | Adek336 | Owned by: | nobody |
---|---|---|---|
Priority: | low | Milestone: | R1.1 |
Component: | Servers/app_server | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
The screen does not redraw itself after leaving KDL in installer CD. Even if F12 will be disabled, a panic might occur in the installer and the user may want continue anyway, then he'd get the ugly artifact (although installing operating systems after a kernel panic is risky business)
Attachments (1)
Change History (9)
by , 16 years ago
Attachment: | img_1881.jpg added |
---|
comment:1 by , 16 years ago
follow-up: 3 comment:2 by , 14 years ago
Component: | - General → Add-Ons |
---|---|
Version: | R1/pre-alpha1 → R1/Development |
comment:3 by , 14 years ago
Replying to diver:
Still here in hrev42124. See also #1421.
It seems that invalidate_on_exit kernel debugger add-on should take this situation into account.
The debugger add-on can't do much about it, it just sends the app_server the notification that KDL was exited. The app_server then marks the whole screen as invalid to trigger a redraw. But since there aren't any windows that actually fill the area behind the installer window this area just isn't redrawn. When booted to the desktop, the Tracker desktop window is there to fill the full area (unless you quit the Tracker as was mentioned above).
The app_server could check for such a situation, or it could just always fill with the desktop background (as it already does when booting). It's not really critical. Far more critical would be to actually fix all the issues that trigger the KDL in the first place...
comment:4 by , 13 years ago
Component: | Add-Ons → Servers/app_server |
---|
comment:5 by , 10 years ago
Priority: | normal → low |
---|---|
Summary: | [InstallerCD] Artifacts after leaving KDL → [InstallerCD] Artifacts after leaving KDL (easy) |
Marking as easy since this sounds like there shouldn't be too much work involved. Also setting priority to low, as I'm even surprised we bothered to implement invalidate_on_exit at all.
comment:6 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:8 by , 4 years ago
Milestone: | R1 → R1.1 |
---|
I think that's because Tracker isn't running. I get the same effect on my Haiku hrev28974 installation when I quit Tracker and then enter and leave KDL.