For information and discussion about Oolite.
https://bb.oolite.space/
Who is this Godwin, and how is he relevant? "Press space commander" is simply wrong, and most definitely does need to have a comma.Tricky wrote:I fear Godwin's law is around the corner.
"Press Space Commander" does not need to be commified (made up word), and even if it did, the original and seminal work that Oolite is based upon did not have the comma.
I guess Tricky is referring to "grammar nazi" and ...Wildeblood wrote:Who is this Godwin, and how is he relevant? "Press space commander" is simply wrong, and most definitely does need to have a comma.
Oh noes, I think I did it!Oolite is based upon Elite. Elite did not have a comma.Tricky wrote:"Press Space Commander" does not need to be commified (made up word), and even if it did, the original and seminal work that Oolite is based upon did not have the comma.
I don't remember BBC Elite (all upper case letters, I think) having a comma in Right on, Commander... but Oolite does (and rightly so).Tricky wrote:Oolite is based upon Elite. Elite did not have a comma.
I already explained why on the previous page.Tricky wrote:"Right on, Commander" is just so wrong. 3 words; why the break in the sentance? Same argument for "Press Space, Commander".
Tricky, you are correct that "Press space commander" is not even a sentence - because it is ungrammatical. "Press space, commander," however, is a sentence.Tricky wrote:In fact, it isn't even a sentance...
It most certainly is not. It is a sentence in the imperative mood. That is easily recognised by the verb (to press) being the first word of the sentence.Tricky wrote:...it's a statement of fact.
You miss the point. It is a statement not a sentance. Or maybe I miss your point and we are arguing different points.Wildeblood wrote:Tricky, you are correct that "Press space commander" is not even a sentence - because it is ungrammatical. "Press space, commander," however, is a sentence.
Hmm, you enthusiastically replied while I was still editing my post.Tricky wrote:You miss the point. It is a statement not a sentance. Or maybe I miss your point and we are arguing different points.Wildeblood wrote:Tricky, you are correct that "Press space commander" is not even a sentence - because it is ungrammatical. "Press space, commander," however, is a sentence.
Nope.. found the culprit, by a process of elimination.cim wrote:Hmm... that suggests that it isn't clearing your HUD successfully, or at least quickly enough. Does it still happen with no OXPs installed?
).Ah - and probably auto shows the HUD on any other screen change, which interferes with the contracts interface trying to manage this.Diziet Sma wrote:It's the Hud Vanisher OXP, which auto-hides the hud when exterior views are selected. Dunno why it would have that effect when docked, but in vanilla trunk, even when it's the only OXP installed, the text appears on that screen.
I'm not sure about that.. because it doesn't affect any other screens when they change.. just that one.cim wrote:Ah - and probably auto shows the HUD on any other screen change, which interferes with the contracts interface trying to manage this.
cim wrote:Ah - and probably auto shows the HUD on any other screen change, which interferes with the contracts interface trying to manage this.Diziet Sma wrote:It's the Hud Vanisher OXP, which auto-hides the hud when exterior views are selected. Dunno why it would have that effect when docked, but in vanilla trunk, even when it's the only OXP installed, the text appears on that screen.
Code: Select all
this.name = "HUD Vanisher";
this.version = "1.0";
this.viewDirectionChanged = function(to,from)
{
if (from === "VIEW_CUSTOM" && to !== "VIEW_CUSTOM")
{
player.ship.hudHidden = false;
return;
}
if (to === "VIEW_CUSTOM" && from !== "VIEW_CUSTOM")
{
player.ship.hudHidden = true;
return;
}
}
this.guiScreenChanged = function()
{
if(guiScreen !== "GUI_SCREEN_MAIN") // <-------- Change here.
{
player.ship.hudHidden = false;
return;
}
}guiScreenChanged() not trigger for missionscreens, because there was no reason for an oxp to react. In trunk guiScreenChanged() now fires also for missionscreens, so it becomes more important for an oxp to check which page is on display.