Celestia Forums

As discussed by Andrea in the following thread, launching a Cel script from a Celx script is not possible yet: http://celestiaproject.net/forum/viewtopic.php?t=11607&start=8

Of course, one can already include Cel commands into a celx script. However, with the new possibilities to set the line and label colors, or to map functions to specific keys via celx scripting, I think that it could be useful and above all handier to have the ability to run one or several celx scripts in a row before launching a start.cel script.

I've already implemented a celestia:runscript command in one of my Celestia builds. Adding this command at the end of a celx script allows launching whatever celx or cel script once the original celx script is done.

Here's a concrete example:


Would you find such a feature useful ?

Vincent wrote:I've already implemented a celestia:runscript command in my own Celestia code. Placing this command at the end of a celx script allows to launch whatever celx or cel script once the original celx script is done. Would you find such a feature useful ?

Yes, please, Vincent, very appreciated.
Bye

Andrea

So this way you can do a "chain" of scripts?
That seems to be interesting...

ElChristou wrote:So this way you can do a "chain" of scripts?
That seems to be interesting...

Actually, this is already possible via the loadfile Lua command, but only for celx (-> Lua) scripts. However, I've noticed that some scripts don't work as expected... Moreover, I find it quite useful and handy to run several specific celx scripts in a row before launching a start.cel script, rather than copying all the stuff in a single script...

Vincent wrote:

ElChristou wrote:So this way you can do a "chain" of scripts?
That seems to be interesting...

Actually, this is already possible via the loadfile Lua command, but only for celx (-> Lua) scripts. However, I've noticed that some scripts don't work as expected... Moreover, I find it quite useful and handy to run several specific celx scripts in a row before launching a start.cel script, rather than copying all the stuff in a single script...

I'm trying to use that function in a LUA module, but currently it isn't working. What is wrong here in the following code ?



I also tried this function :


I'm simply trying to execute a CELX script file from within a LUA (i.e. CELX) module...

Cham wrote:I'm trying to use that function in a LUA module, but currently it isn't working. What is wrong here in the following code ?

Martin,

First of all, all these issues we're having when trying to launch a script from within another
with the dofile() or loadfile() Lua functions will be eventually fixed in Celestia 1.6.1 using
the celestia:runscript method.

Then, the following reasons could explain the fact that your script above is not working:
1- The loadfile() function only compiles the chunk of Lua code but does not run it, and thus,
one has to write:

I'd suggest to use the dofile() function instead, which is more straightforward:


2- Lua uses the celestia base directory to look for files.
As a workaround, I've written my own function that returns the path of the Lua directory
from which I run my Lua scripts.


Then you can run your script using:


3- As we discussed recently (see: viewtopic.php?f=9&t=15718&start=12 ),
your celx script shouldn't contain any wait() or createcelscript command.

Vincent,

the dofile() command is now working. Thanks a lot !

Now, what will be the difference between the dofile() and the new celestia:runscript() command ?

Cham wrote:the dofile() command is now working. Thanks a lot !

Good, you're welcome!

Cham wrote:Now, what will be the difference between the dofile() and the new celestia:runscript() command ?

The Lua dofile() function runs the content of the script to launch as a Lua chunk that is not
recognized by the celestia core as a standard celestia script. And thus, special commands like
wait() or celscript:tick() are simply ignored. This can be quite annoying since the wait()
command is pretty frequently used.

The celestia:runscript() method will fix that.

Vincent wrote:Lua uses the celestia base directory to look for files.
As a workaround, I've written my own function that returns the path of the Lua directory
from which I run my Lua scripts.

Code: Select all

local getLuaDirPath =
    function(dir)
        local pathes = package.path;
        local c0, c1 = string.find(pathes, dir);
        local path1 = string.sub(pathes, 1, c1);
        local revpath1 = string.reverse(path1);
        local c2 = string.find(revpath1, ";");
        local revpath2 = string.sub(revpath1, 1, c2 - 1);
        local path = string.reverse(revpath2);
        return path;
    end

Then you can run your script using:

Code: Select all

local scriptpath = getLuaDirPath(myLuaDir).."/"..myLuaScript;
celestia:runscript(scriptpath);

Vincent,

Is this all the available information on this new 161 celestia method?
Do you probably have some aditional info, so we can update the celx wiki page on this new method as accurate as possible?

e.g.
may scriptpath in your example also be a string relative to the base directory or may it even be in the root as you wish?
Are there probably more parameters not mentioned in the above example?
...

Marco

The celestia:runscript method is in SVN now.

Marco Klunder wrote:Is this all the available information on this new 161 celestia method?
Do you probably have some aditional info, so we can update the celx wiki page on this new method as accurate as possible?

Marco,

Thanks for your help on keeping the Lua/Celx wiki page up-to-date.

So far, the script absolute path is required, but we still have time to make celestia:runscript
use a path relative to the main celx/lua script, instead. We just need to agree on this...

Now if we stick with using an absolute path, the script to launch will be still located in the same
directory as the main script -- or in a sub directory. Thus, some precision might be needed
about how to get the path of the main script. The process is different in a CELX script
than in a LUA script.

- Getting the path of a CELX script

Then, we can launch our celx script using:

Note that in a celx script, the celestia:runscript method should be always followed by
a wait(0) command.


- Getting the path of a LUA script
Lua uses the celestia base directory to look for files, and thus we can't use the celestia:getscriptpath()
command here since it will return the path of the celestia base directory (= package.path variable).
So we need to write our own function to get the main Lua script path :


Then, we can launch our celx script using:

Vincent, thanks for this update

Vincent wrote:So far, the script absolute path is required, but we still have time to make celestia:runscript
use a path relative to the main celx/lua script, instead. We just need to agree on this...

I don't want to interfere with the development, but probably a 2nd parameter in the runscript method can be used to determine wether the scriptpath is absolute or relative ...

Marco

Marco Klunder wrote:I don't want to interfere with the development, but probably a 2nd parameter in the runscript method can be used to determine wether the scriptpath is absolute or relative ...

I just commited a fix that makes celestia:runscript use relative file pathes only.
I don't see any case where an absolute path should be prefered over a relative one.
That will make things much simpler: no more need to get the main script path and
no more difference between Lua and Celx scripts. Moreover, this is more consistent
with other methods like celestia:loadtexture which also use relative file pathes.

Here's an example where the main script and the script to launch are located in
the same dir:



Notes:
- Even on Windows, use slashes "/" in the script path (when the script to launch is located in a different dir):

- The main script will be terminated as soon as the second script is launched.
That means that all extra lines of codes below the celestia:runscript command
will be ignored.

Very nice enhancements.
Could it be possible to make a division between loading and executing a script?
It can avoid some overhead on the moments it matters.
It would be handy to load a script at the background while one is still playing.

You're doing great work here. Please don't stop, but keep going

duds26 wrote:Could it be possible to make a division between loading and executing a script?
It can avoid some overhead on the moments it matters.
It would be handy to load a script at the background while one is still playing.

There's no built in method in Celestia core that loads a script without running it.
So I'd suggest to use the Lua loadfile function which compiles the chunk of Lua code before
running it:



As precised all along this thread, the wait() command can't be used in a chunk of Lua code, though...