Hi Thomas
Very cool, I would like to ask with regards to the MP3 player, how can I get the music to repeat?
The new pointers are a nice touch and I will be creating my own very soon.
Pano2VR is amassing and keeps on getting better, many thanks.
When I drop a QTVR on the input field of beta 6, or when using the import button, then all User Data is gone, when I input an equirectangular then the User Data is not removed.
I hope this is not a feature but a bug and that it can be repaired.
Wim.Koornneef wrote:
When I drop a QTVR on the input field of beta 6, or when using the import button, then all User Data is gone, when I input an equirectangular then the User Data is not removed.
I hope this is not a feature but a bug and that it can be repaired.
It's not a bug, it's a feature! If you load a QTVR it takes the embedded userdata as default values.... I will make an option in beta7 to disable this.
I think it would be helpful if you rationalized your numbering scheme.
I personally find a letter appended to a number that is a beta release version of a projected main line version release number to be ... confusing.
Please consider using a numbering system that is more mainstream.
For example, "2.0b6" would be the 6th pre-release version of version 2.0. If a small flaw was found in b6, the next release is either "2.0b7" or "2.0b6.1" [or something]. It should never be something like "2.0b6b!"
That approach leads to crazy identifiers like "2.0b6b3a4." Yuck!! Please, no letters in the version identifier other than "b" for "Beta," or "a" for "Alpha," and so forth.
Some developers include the build number also, which helps even more to make things clear.
If you load a QTVR it takes the embedded userdata as default values.... I will make an option in beta7 to disable this.
