Re: Re: Re: overlays with luxor

Salut Valerie,

>   Thanks for your answer : it could be a good
> solution.
>   But I have some problems to make it work in my
> context, which is
> tabpanels:
>       I add the following line into my xul file :
>             <tabpanels>
>             #include("myfile.txt")
>             ...
>             </tabpanels>
>       and create myfile.txt in the same directory :
>             <tabpanel>
>             ...
>             </tabpanel>
> 
>   But when the xul loader parse this directory, it
> also try to load
> myfile.txt like any other file, and then I get an
> error !
>   Is there any solution to avoid the parsing of this
> file or can it be
> placed anywhere else ?


  Yes, the standard built-in chrome loader only picks
up files in the startup directory tree. Thus, if you
put your include files outside the startup directory
everything works fine (e.g. lib/myfile.txt instead of
startup/myfile.txt).

  As an alternative you can choose a different chrome
loader using your own file filter, for example.

  If you run into any trouble let me know.

  - Gerald


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf