Re: PTViewerNG - High resolution example
- --- In PanoToolsNG@yahoogroups.com, Michel THOBY <thobymichel@...> wrote:
>Rounding errors at the cube edge, a problem with cubic viewers since they exist. There is no good solution other than that the underlying opengl implementation is accurate which is not always the case.
> Hi Helmut,
> Strange: One may see a faint white dotted line in the canal of the higher resolution panorama:
In my cube viewers (PTViewer, PTViewerME, PTViewerNG) I provide for a small ( a few pixel) overlap at the cube edges to hide inaccuracies, but obviously not enough for your computer. There are no lines in my setups. You can try for yourself: in line 192 of ptviewer.js
var f = 0.998;
try smaller values (0.997 0r 0.996) until the lines dissapear. The larger this overlap, the larger is the risk that some other artefact may appear.
- --- In PanoToolsNG@yahoogroups.com, "ahoeben41" <aldo@...> wrote:
>Just a leftover of my debugging session until I found out that it didn't work because of the offsetX-thing. I guess I will reinsert the "return false" statements.
> I see you removed the "return false" statements from the handleMouse[Down|Up|Move] handlers. I put those there to prevent accidental selections of html elements outside the canvas element. Come to think of it, you only need it for the handleMouseMove handler, and only if currentlyDragging is set.
> Or does that break things in Firefox? (Ah, brings back memories of the "good old days" of cross-browser testing...)