Textures in SVN's

[Guckytos]

what about a good description of what the key does? Where do you get this from?

A description with examples of what every key in Celestia does and cel/URL's that a reader can click on to see the key's effect, is already in the Users Guide, which is currently available via hyperlink from the main Celestia website and the Motherlode.

A shorter version of it focused just on the keys, could be written in or converted to PDF or HTML and included with the default distribution, with access to it as a link in the Help menu.

If the development team felt that would be the best idea, I would be happy to work on it.

Frank

Hmm, Frank I think there is a misunderstanding here.

What I was referring to was the automated generation of the keyboard shortcuts as a readme, that bdm was talking about before.

My question was, where would the automated generator get the good information for a newly introduced shortcut from?

And what you are proposing is already being done here http://shatters.net/forum/viewtopic.php?f=2&t=12930, so that would be double work, what you are proposing, I think. I only have not very much time to finish it at the moment. So I think it will have to wait for 1.6.1 and also because the translators would need time to translate it.

Best regards,

Guckytos

[mjoubert]

Christophe, Martin,

An alternative is to add a celx function that sets the textures resolution, such as:

Code: Select all

celestia:settexturesresolution("medium")

This way, you will be able to map this function to any key (including r/R) using your start.celx script.

Does this sound reasonable?

Vincent,

I'm now using the command settexturesresolution. I think it's useful to select the resolution in a startup script.

In the same way, I'd like to be able to select an alternative surface (i.e. BMNG) in a startup script with a command like

Code: Select all

setalternativesurface {  object "/sol/earth" surface "BMNG 128K" }


Does it already exist ? Is it possible to add it ?

Maybe I can do it by my own if you want to.

Thanks,

Mathieu

[chris]

Mathieu,

This function exists already: observer:setsurface(). The fact that it's a method of observer is probably why you didn't notice it immediately:

http://en.wikibooks.org/wiki/Celestia/C ... setsurface

You'd use it like this:

Code: Select all

celestia:getobserver():setsurface("BMNG 128K")


Note that you can't set the surface per object. In the above example, any object without a surface named 'BMNG 128K' would just appear with its default texture.

--Chris

[mjoubert]

Thank you Chris,

(difficult to answer faster than you did !)

[Vincent]

The setttextureresolution function is now available in the 1.6 development version
both for celx and cel scripting. It takes a number argument in celx (0 | 1 | 2)
and a string argument in cel ("low" | "medium" | "high"). We opted for a number
argument in celx in order to allow the use of code like:

Code: Select all

celestia:settextureresolution(celestia:gettextureresolution() + 1)

CELX example:

Code: Select all

-- Title: change texture resolution using R key

function changeTextureRes()
    texRes = celestia:gettextureresolution()
    if texRes == 2 then
        texRes = 0
    else
        texRes = texRes + 1
    end
    celestia:settextureresolution(texRes)
end

keyhandlers =
{
    R = changeTextureRes
}

function handlekey(k)
    handler = keyhandlers[k.char]
    if (handler ~= nil) then
        handler()
        return true
    else
        return false
    end
end

celestia:registereventhandler("key", handlekey)

CEL example:

Code: Select all

{
settextureresolution {resolution "low"}
wait {duration 3}

settextureresolution {resolution "medium"}
wait {duration 3}

settextureresolution {resolution "high"}
wait {duration 3}
}

[ElChristou]

Tx Vince!
I'll update my source and test out later today.

[ANDREA]

The setttextureresolution function is now available in the 1.6 development version both for celx and cel scripting.

Thanks a lot, Vincent, very appreciated by all poor cel users.
Bye

Andrea

[mjoubert]

Works as expected in a Tcl script that generated a .cel startup script.

Code: Select all

   # D?finition du niveau de textures
   if { $texturesLevel == "high" } {
      puts $id "   settextureresolution { resolution \"high\" }"
      puts $id "   setsurface { name \"128K Blue Marble Next Generation\"}"
   } else {
      puts $id "   settextureresolution { resolution \"medium\" }"
      puts $id "   setsurface { name \"Normal\"}"
   }


[ElChristou]

Oops, I forgot to post, sorry... All is ok, many tx for this script feature!

[bdm]

BTW. The dropdown keyboard shortcuts (Help menu) is now out of date.

Is it possible to build the Help menu in code from the same resources that the application uses for the shortcuts themselves? That way, if the keys change, the Help menu is updated automagically.

How would you do that? I mean, you would get the keys, but what about a good description of what the key does? Where do you get this from?

If the code had an appropriate structure to store this information, it can be provided as a part of the structure by the developer.

Suppose the structure had the following definitions:

Code: Select all

ShortcutKey: Keytype;
Description: string;
BoundFunction: celfunction;

Then the application would use the ShortcutKey to execute the BoundFunction, and the part of the application that builds the Help menu would convert the ShortcutKey to human-readable text with a function, and then append the Description. If the ShortcutKey changes, the Help text is also changed at the same time. This approach eliminates bugs caused by the Help text and the code getting out of sync.