Avoiding sf::View's float precision, and visible sprites

[Manux]

Hello, I actually have 2 little questions:

First, I'm making a 2D isometric tile engine, and, as I experienced it before with OpenGL, giving a float position to a textured quad will result in a white border around it, which is quite unappealing... I'm having the same problem with SFML right now.
Do you know any way around this?

Second, I wondered what's the most efficient way of selecting only visible sprites in my tilemap?

[Laurent]

First, I'm making a 2D isometric tile engine, and, as I experienced it before with OpenGL, giving a float position to a textured quad will result in a white border around it, which is quite unappealing... I'm having the same problem with SFML right now.
Do you know any way around this?

Well, it's not related to float coordinates. It actually depends on a lot of things. One workaround that usually works is to disable texture filtering (image.SetSmooth(false)).
Have you tried SFML 2?

Second, I wondered what's the most efficient way of selecting only visible sprites in my tilemap?

I'd do it with simple AABB tests.

[Manux]

Merci  

[Nexus]

Second, I wondered what's the most efficient way of selecting only visible sprites in my tilemap?

I would recommend AABB (probably rectangle) checks as well. However, objects that are arranged in a systematic manner (like tiles) can be tested faster. When they're stored in a 2D-container, calculate the minimum and maximum indexes and just draw the required sprites in two nested for loops.