You are not logged in.

"include" behaviour has been changed in pr16

ily

Beginner

  • "ily" started this thread

Posts: 3

  • Send private message

1

Wednesday, August 22nd 2018, 7:35am

"include" behaviour has been changed in pr16

Hello everybody


i used a lot of "includes" in my template. So now i decided to move to pr16 and my template does not work.



now i have to start every xml with <krpano>
almost everything was fine till i came to layers


now structure like
<layer name="skin_main">
<include url="social.xml"/> (social.xml contains set of layers)
</layer>
does not work anymore


with <krpano> tags it just does not includes
without it there is xml parsing failure


are there any solution for that?

indexofrefraction

Professional

Posts: 1,362

  • Send private message

2

Wednesday, August 22nd 2018, 9:20am

Source code

 
1
2
3

<layer name="skin_main">
    <include url="social.xml"/> (social.xml contains set of layers)
</layer>

that was really possible without the full xml tree (in social.xml) ?
zFilter plugin -- zFlare plugin -- zSnapshot plugin

ily

Beginner

  • "ily" started this thread

Posts: 3

  • Send private message

3

Wednesday, August 22nd 2018, 10:21am

Quoted from "indexofrefraction"

Source code

 
1

     (social.xml contains set of layers)

that was really possible without the full xml tree (in social.xml) ?
yes. that still works with pr14

social.xml looks like

Source code

 
1
2
3
4

<layer name="social_btns" keep="true" align="leftbottom" width="150" height="100%" visible="true" type="container" > 
    <layer name="twitter_btn" url="twitter.png" keep="true"
        etc...
</layer>


and i haven't to update every tour if i decide to change something in layout.

klaus.krpano

Administrator

Posts: 13,499

  • Send private message

4

Sunday, September 2nd 2018, 8:43pm

Hi,

each xml files needs to contain a <krpano> root xml element.

In older versions it was also partially working without when there was only one xml element in the xml file, but that was never considered as correct or as supported.

Because of changes in the xml parsing and to be able to detect if decrypting an encrypted xml files was successful, the xml parser needs now to be more strict here.

Best regards,
Klaus

Similar threads