Annotations plugin

Quote from kme

Everything seems to work fine with 1.22 We will have to adjust documentation to include the "sameorigin" parameter in the embedpano, but after that, things should work fine.

If you purchased the license for the annotations plugin and the overlay is not being removed after setting your license, please reach out in direct message or by e-mail kristof @ kri-soft.be

gr,

Kristof

Thank you. kme-san.

I thought I had given the krpano version for a tour that had no problems up until now, but I may have made a mistake.
I'll check.

Quote from kme

Everything seems to work fine with 1.22 We will have to adjust documentation to include the "sameorigin" parameter in the embedpano, but after that, things should work fine.

If you purchased the license for the annotations plugin and the overlay is not being removed after setting your license, please reach out in direct message or by e-mail kristof @ kri-soft.be

gr,

Kristof

Hi. kme-san.

Even with krpano1.22, I was able to run it as before.

However, there was a problem, so I would like to report it.

annotations_1.20

mousehandler.xml
File not found. Was that what you intended?
It seems like you can't zoom without this.
(It's not in the downloaded file.)

A license error was always displayed because Mousehandler.xml was loaded.

Authentication for mousehandler.xml is "<settings name=".
The current license authentication for annotations is "annotationsettings name=".

I configured both and it worked.

Thank you.

Sorry for my bad English.

Hello kme ! I found your annotations plugin. It does a great job at adding visual information callouts, and I was especially pleased to see the live editor that is included. Great work!

After reviewing the documentation, and testing for some time, I have a few questions about functionality I would like to ask.

1. Can the annotations be fully transparent when behind geometry?

   • I have tried updating the alpha_* values inside <annotationsettings> as follows:

     Code

     <annotationsettings name="annotations"
     	alpha_css="color: rgba(255, 255, 255, 0); font-size:16px; text-align:center; font-weight:bold;"
     	alpha_bgcolor="0x00000000"
     	alpha_bgborder="2 0xffffff 0"
     />

   • It seems that the callout’s distance line and the circle remain semitransparent and visible. Is there an option to hide the callout and distance line completely when behind geometry?
2. Can the annotation-locations file or infopanel text be changed at runtime?
   • I am considering how this may work with multi language support. Are you aware of a way that I can change the annotation-locations.xml file in use during runtime, or another way which I may be able to update the infopanel text based on a change?

Thank you for sharing this plugin, and for taking the time to review these questions.

Best Regards,

ClassOutside

Thank you! I look forward to your response!

Hey kme , I found a solution to one of the questions and thought I would update here.

Question: Can the annotation-locations file or infopanel text be changed at runtime?

Answer: Yes! According to the Krpano XML documentation xml elements can be redefined, and the newest declaration will overwrite the previous ones. This means multiple annotation-locations.xml files can be created for each language (ex: annotation-locations_fr.xml, annotation-locations_de.xml). At runtime we can call includexml(annotation-locations_fr.xml), this will overwrite the current fields. To redraw the layers invalidatescreen() can be called and the annotation text appears to update.

I am still unsure how the annotations may be made fully transparent and not clickable when behind geometry. Perhaps this feature may be available by changing the depth buffer? I am unsure.