Originally posted by mikesinghI can not know for sure how things happened, but this is what I think.
So the question is, was the anomaly removed from ver. 2.0 of the CB? If not, then what or why did that anomaly show up in the first place? What exactly was it? Tape, paper clip, spilled coffee or just a glitch? Now that is the proof I require!
Those images on the browser, regardless of version, do not exist. When we choose any resolution, only when we choose the resolution that corresponds to that of the photos available for that area can we see the real photos. If we choose a different resolution then the software must look for the photos available for that area, join them, and send them as one image for our web browsers.
And is in this step that I think that the problem is. The first version of the image browser did not worked as it should when joining the images, especially when it was for an area for which on or more images are missing, that is why it created those strange grey areas.
The images used on both versions, as I said before, are the same and available on that site to which I pointed more than once and from which I get the images when I need.
So, in my opinion, and in this case I can say in my professional opinion as a programmer, the strange images from the previous version of the image browser are the result of bad programming.













