Zandronum Chat on our Discord Server Get the latest version: 3.1
Source Code
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001377Zandronum[All Projects] Suggestionpublic2013-06-23 14:482014-06-14 17:23
ReporterKonar6 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusfeedbackResolutionopen 
PlatformOSOS Version
Product Version1.0 
Target VersionFixed in Version 
Summary0001377: Suggestions for client console notify lines, part 2
Description Why is C_FlushDisplay() called in g_level.cpp:1022 and g_level.cpp:1579 (ie. on level finished and level start)?
 This prevents players from seeing essential stuff without manually checking it in console, such as who exited the level, any last-second chat, the new level name...
 I very much like the notify buffer not being interrupted and was thinking that others might find keeping the buffer useful too.
 Note: other ports (ZDaemon and Odamex) don't flush the notify buffer on level finished.
Attached Files

- Relationships
related to 0001236closedDusk Suggestions for client console notify lines 

-  Notes
User avatar (0006486)
Dusk (developer)
2013-06-23 14:49
edited on: 2013-06-23 14:51
Quote from "Torr Samaho"

Quote from "Konar6"

Why is C_FlushDisplay() called in g_level.cpp:1022 and g_level.cpp:1579 (ie. on level finished and level start)?


 g_level.cpp:1022 was already in the source of ST 97c2, so it was added to Skulltag before I took care of the source, g_level.cpp:1579 is inherited from ZDoom. I don't know the motivation of either.


Quote from "Qent"

Make it optional with con_flushonlevelchange? I would like to keep the display uninterrupted (mostly for not missing chat messages online), but I could totally see someone wanting to keep a more vanilla feel (e.g. does it carry pickup messages into the intermission in singleplayer?).
User avatar (0009297)
Watermelon (developer)
2014-06-14 17:23

 Is this changed to work in 2.0?

Issue Community Support
Only registered users can voice their support. Click here to register, or here to log in.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2013-06-23 14:48 Dusk New Issue
2013-06-23 14:48 Dusk Reporter Dusk => Konar6
2013-06-23 14:48 Dusk Summary Suggestions for client console notify lines 0000002 => Suggestions for client console notify lines, part 2
2013-06-23 14:49 Dusk Note Added: 0006486
2013-06-23 14:49 Dusk Relationship added related to 0001236
2013-06-23 14:51 Dusk Note Edited: 0006486 View Revisions
2013-06-23 14:52 Dusk Product Version => 1.0
2013-06-23 14:55 Dusk Severity minor => feature
2014-06-14 17:23 Watermelon Note Added: 0009297
2014-06-14 17:23 Watermelon Status new => feedback




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker