Probable Noob question

[ElChristou]

Why do we keep the LabelledStars entries in celestia.cfg?

[rthorvald]

Why do we keep the LabelledStars entries in celestia.cfg?

So you can label your own stars...

- rthorvald

[ElChristou]

Why do we keep the LabelledStars entries in celestia.cfg?

So you can label your own stars...

- rthorvald

??

Wasn't the LabelledStars to label stars before the general implementation of stars' label?

[Hungry4info]

Indeed. Now stars are labeled in accordiance with their visual magnitude. I guess there's no real reason to keep a list of stars to lable.

[ElChristou]

Another one: is there a good reason to always display the speed (bottom left corner)? I mean why not displaying it only if positive? (it could stay at zero a few seconds then fade out?)

[ElChristou]

Another one: is there a good reason to always display the speed (bottom left corner)? I mean why not displaying it only if positive? (it could stay at zero a few seconds then fade out?)

Seems this one was really a noob one... then someone can enlighten me?

[BobHegwood]

Don't know about others, but I actually like this feature. Rather
interesting to see the real time-scales necessary in order for us poor
slow-witted humans to notice changes in the Universe.

I suppose that you could modify this feature to be selectable or such,
but I personally don't see the need. Just my opinion though.

Thanks, Brain-Dead

[ElChristou]

Don't know about others, but I actually like this feature. Rather
interesting to see the real time-scales necessary in order for us poor
slow-witted humans to notice changes in the Universe.

?? Bob, I think I don't follow you well... What are you talking about??

[Vincent]

Another one: is there a good reason to always display the speed (bottom left corner)? I mean why not displaying it only if positive? (it could stay at zero a few seconds then fade out?)

Chris,

That can be done using, e.g., the following celx script, which furthermore is a simple tick event handling example:

Code: Select all

-- Title: Toggle speed overlay element (tick event handling example)

function toogleSpeedOverlay()
   t = celestia:getoverlayelements()
   celestia:setoverlayelements{Velocity = not(t.Velocity)}
end

function handletick()
   speed = math.abs(celestia:getobserver():getspeed())
   showSpeed = celestia:getoverlayelements().Velocity
   if (speed > 1e-12 and not(showSpeed)) or (speed <= 1e-12 and showSpeed) then
      toogleSpeedOverlay()
   end
end

celestia:registereventhandler("tick", handletick)

Sorry, no fading effect available (yet), though...

[ElChristou]

Vince, before talking about code, I really would like to know what is the reason (they must be one!) to have the speed always displayed. Now if there is no particular reason, then if it's reasonable to remove after a few seconds the display.

Perso I think that it could be removed, but perhaps I'm forgetting something, it's why I'm asking...

[Vincent]

Vince, before talking about code, I really would like to know what is the reason (they must be one!) to have the speed always displayed. Now if there is no particular reason, then if it's reasonable to remove after a few seconds the display.

Chris,

This isn't a piece of C++ code, but a simple Celx script that can be added to your start.celx file in order to do the trick you requested...

[BobHegwood]

Another one: is there a good reason to always display the speed (bottom left corner)? I mean why not displaying it only if positive? (it could stay at zero a few seconds then fade out?)

You don't follow me well?

I LIKE THIS FEATURE... Is that plain enough?

[ElChristou]

You don't follow me well?

Yes Bob, I'm really sorry but with this comment of yours:

Rather interesting to see the real time-scales necessary in order for us poor slow-witted humans to notice changes in the Universe.

(probably I don't understand, but) actually I don't see the relation between the speed of the observer and the changes in the Universe within Celestia...

The only feature I see related to changes of the scene in time is the Time setting itself...

So yes I don't follow you well and I'm sorry...

**

Now, the only reason I can think about keeping the display, would be some kind of reminder for the feature... Is that a valid enough reason?

[ElChristou]

Vince, before talking about code, I really would like to know what is the reason (they must be one!) to have the speed always displayed. Now if there is no particular reason, then if it's reasonable to remove after a few seconds the display.

Chris,

This isn't a piece of C++ code, but a simple Celx script that can be added to your start.celx file in order to do the trick you requested...

Oops, ok then, I'll give a go to see...

[chris]

Indeed. Now stars are labeled in accordiance with their visual magnitude. I guess there's no real reason to keep a list of stars to lable.

Yes, LabelledStars should be removed from celestia.cfg. It is no longer used.

--Chris

[BobHegwood]

Rather interesting to see the real time-scales necessary in order for us poor slow-witted humans to notice changes in the Universe.

(probably I don't understand, but) actually I don't see the relation between the speed of the observer and the changes in the Universe within Celestia...

The only feature I see related to changes of the scene in time is the Time setting itself...

So yes I don't follow you well and I'm sorry...

**

Now, the only reason I can think about keeping the display, would be some kind of reminder for the feature... Is that a valid enough reason?

Well, maybe we're just not talking about the same feature? I
enjoy being able to see how fast one has to go in order to get to
a particular location even within the Solar System. Even at the
speed of light it takes a while to get to Mars. You understand
what I mean?

Sorry myself... I'm just a very grumpy old man as you oughtta
know by now.

[ElChristou]

Well, maybe we're just not talking about the same feature? I
enjoy being able to see how fast one has to go in order to get to
a particular location even within the Solar System. Even at the
speed of light it takes a while to get to Mars. You understand
what I mean?

No... (kidding!)

Ok, we are talking about the same, but I never said to eliminate the display, just to eliminate it WHEN you don't move (Speed: 0.00000m/s)...

If you try Vincent's celx code you will see what I mean...

(For now I'm using it and I find it pretty cool...)

[BobHegwood]

And I simply said that I liked the feature...

[chris]

Well, maybe we're just not talking about the same feature? I
enjoy being able to see how fast one has to go in order to get to
a particular location even within the Solar System. Even at the
speed of light it takes a while to get to Mars. You understand
what I mean?

No... (kidding!)

Ok, we are talking about the same, but I never said to eliminate the display, just to eliminate it WHEN you don't move (Speed: 0.00000m/s)...

If you try Vincent's celx code you will see what I mean...

(For now I'm using it and I find it pretty cool...)

I agree that this is nice--it's good to have a clear visual indication when the observer is moving.

--Chris

[Vincent]

If you try Vincent's celx code you will see what I mean...

(For now I'm using it and I find it pretty cool...)

Christophe,

I think you'll like the following version even more: the speed overlay element remains visible for 2 seconds before disapearing when speed is nil:

Code: Select all

-- Title: Toggle speed overlay element (tick event handling example)

celestia:setoverlayelements{Velocity = false}

t0 = 0

function handleSpeedTick()
   speed = math.abs(celestia:getobserver():getspeed())
   showSpeed = celestia:getoverlayelements().Velocity
   if (speed > 1e-12 and not(showSpeed)) then
      celestia:setoverlayelements{Velocity = true}
   end
   if speed <= 1e-12 and showSpeed then
      if t0 == 0 then
         t0 = celestia:getscripttime()
      elseif celestia:getscripttime() >= t0 + 2 then
         celestia:setoverlayelements{Velocity = false}
         t0 = 0
      end
   end
end

celestia:registereventhandler("tick", handleSpeedTick)