I need to use this in a std::map but am being prevented by operator deletion

[benajaero]

I'm using a manager to store my game maps. The code is similar to this.

//_maps is an std::map. name is a string
tmx::Map _map
MapManager::_maps[name] = _map;

Fails because of operator deleted. So I got rid of that code and am directly storing maps in my game controller. However, I cannot keep loading the map each cycle as that is cpu intensive. I therefore tried to place the maps as private values in the controller but I get this error.

                                                                                            [5/9038]
./include/playing.h:14:18: note: copy constructor of 'PlayController' is implicitly deleted because field '_outerWorld' has a deleted
      copy constructor
        tmx::Map _outerWorld;

./include/tmxlite/Map.hpp:96:9: note: 'Map' has been explicitly marked deleted here
        Map(const Map&) = delete;

How can I get around this? I tried deleting the Map code but it leads to even more errors. Note std::map insert does not work for some reason

[fallahn]

My bad, Map was missing its move assignment / move constructor. I've updated the the repository and you can now do

_maps.emplace("map_name", tmx::Map());

or

_maps["map_name"] = tmx::Map();

[benajaero]

Ok it works now. Thanks very much.

[benajaero]

The problem is also evident in MapLayer but I managed to fix it by using the code you added for Map.

[benajaero]

Ok MapLayer still doesnt work

[fallahn]

What is 'MapLayer'? There is ImageLayer, TileLayer and ObjectGroup all of which inherit Layer. The vector of layers in the Map class contains unique_ptrs which will make it inherently non-copyable. Perhaps you should think of tmx::Maps like other resources such as textures or shaders - load them once into your std::map/resource holder, then pass references to them around your program, avoiding any attempted copies.

[benajaero]

No. I'm talking about MapLayer in SFMLOrthogonal. That's what I plan to do.

[fallahn]

OK Sorry, I forget there were some examples :) To be honest I wouldn't use them in production code, they are merely there to demonstrate how you might make a drawable from a map layer using vertex arrays. For now you could temporarily remove the deleted constructor/assignment operator lines, although you may run in to other problems further down the line, but you'd at least be able to get something drawing. Vertex arrays are also notorious for the 'tearing' problem, so you may want to implement a renderer using this technique instead.

[benajaero]

Oh, ok. Are there any prebuilt renderers I could use (compatible with this) or must I create my own?

[fallahn]

Other than the examples I don't have any, but you may be able to find someone else using the library and ask them. The general idea is that the lib only parses tmx data into a C++ data format - what you do with the data is up to you, so it can be made to best suit your project.

[benajaero]

Hey, I noticed in the SFML Orthogonal the tile map stops rendering past a certain distance when scaled.

[fallahn]

Quite possibly related to #14 and #23

[benajaero]

I think the problem is that I'm scaling 16 x 16 tiles to a SCALE variable. I'm not exactly sure how to fix this issue.

[fallahn]

Ah - presumably you're applying the scale to the transform contained in the sf::RenderStates passed to the draw function? If this is the case updateView() will need the scale applied to it too, so that it's large enough to account for the scaled up chunk size (I think) or apply the scale to the chunksize value to get the appropriate count from the view

[benajaero]

int posX = static_cast<int>(std::floor(viewCorner.x / (m_chunkSize.x * SCALE)));
int posY = static_cast<int>(std::floor(viewCorner.y / (m_chunkSize.y * SCALE)));

I've tried changing this but now it only renders about half of the map the turns white.