Page 3 of 3

Re: Custom view doesn't work in 2.5.8

PostPosted: Sat Dec 23, 2017 3:49 pm
by bobjones
2.5.9 was (finally) released several days ago.

Re: Custom view doesn't work in 2.5.8

PostPosted: Sat Dec 23, 2017 3:58 pm
by Maukoop.nl
Thanks, I noticed it this morning. I'll check it out.

It would be nice though, to hear something about the software development. Panotour is relying on KR Pano. Are there any plans about developing a new program without being relying on this, or are the priorities at 360 videos, panobooks and Go Pro?

Some insights would help considering business decisions. I understand mayor updates would be paid updates. But don't let me hang too long without communication. How much does it take to send users an e-mail with a roadmap?

Re: Custom view doesn't work in 2.5.8

PostPosted: Sun Jan 14, 2018 1:59 pm
by 360panosi
Yes, the 2.5.9 is released. But if Im right, the bug for custom hot spot view wasnt fixed. So? Kolor? What are you doing? Are we realy must jump to Pano2VR? Decide what you want. Because clock is RUNNING OUT.

Re: Custom view doesn't work in 2.5.8

PostPosted: Sun Jan 14, 2018 2:20 pm
by signmaster
I just checked and the bug appears to be fixed in 2.5.9

Steve

Re: Custom view doesn't work in 2.5.8

PostPosted: Sun Jan 14, 2018 2:40 pm
by 360panosi
Hm. Wierd. What OS are you using? Windows or OS X? On my Mac after build all custom view hotspot are on defualt view.

Re: Custom view doesn't work in 2.5.8

PostPosted: Thu Jan 18, 2018 11:33 am
by ThomasK
Spotted this thread today - still non official answer from Kolor about a further development of Panotour?

BTW, my thread at viewtopic.php?f=92&t=37624 about deactivating plugins for mobile is not solved. It got closed by the admin to avoid further discussions...

Re: Custom view doesn't work in 2.5.8

PostPosted: Sun Jan 28, 2018 11:57 pm
by signmaster
Hi 360panosi
I am using Windows 10 64bit on an old i7 PC

Steve

Re: Custom view doesn't work in 2.5.8

PostPosted: Thu Feb 01, 2018 5:29 pm
by Annis
The custom view issue was fixed in 2.5.9.

I left the sticky up because I thought this was not the case. So I've removed the sticky status.