Bug: Tiled 0.7.1 for OS X that locks stamp brush tile location

[exactspace]

This may be QT specific or even OS X build specific. Unfortunately I have not found the steps necessary to reproduce this issue. It usually first occurs when I load a project, and select the stamp brush tool. Immediately a tile is drawn the upper left corner of my canvas. If I select the eraser, it immediately erases the tile without clicking anywhere on the canvas. Clicking back on the brush tool draws a tile again the same place. Clicking elsewhere on the canvas may not draw anything. But when it does, the last draw location is highlighted and stuck on the screen, and depending on what tools I choose (the stamp brush or eraser) it will either draw or erase on that same location. It's as if my mouse button is stuck down on the last location instead of releasing. Sometimes I can "break free" of this problem, but I'm not sure what the process is.

[bjorn]

I've never seen this issue on Linux or Windows. Maybe @mpjeff can try to reproduce it on Mac OS X.

[exactspace]

Cool thanks, he says he's going to look into it soon.

[mpjeff]

I haven't been able to reproduce this on Tiled 0.7.1 for OSX 10.6 or 10.7 :(

If you can find a reliable way to get this to happen (it may depend on the map you're opening as well), I can try again.

[exactspace]

I'm not really positive what the steps would be, but I can tell you the details of my situation:

-8 projects open as separate tabs
-Each have 4 tilesets
-Each have 8 tile layers and 1 object layer on the top
-Tile size of 16x16 px
-Seems to happen after switching between projects that have a larger height than width, but I'm not entirely sure.

Thanks

[stefanbeller]

Does this error still occur with version 0.8?

[plangworthy]

Not 100% sure if its the same issue, I used to have this issue with 0.7.1 and now get a similar issue in 0.8. I am using Tiled 0.8 on OSX. Seems to be related to tab browsing. After starting Tiled, the map that is first loaded can be edited OK, but when switching to a map in another tab, no editing can be performed. The stamp cursor does not even appear. I have to close and re-start Tiled in order to edit another map. This happens to me somewhere between 95 and 100% of the time.

In my experience the related 0.7.1 bug also had something to do with tab browsing.

[exactspace]

plangworthy thanks for being someone else that can point this out. I'm curious if it's true on your end that the stamp cursor doesn't show up. For me, it shows up, but it's usually stuck in the upper left.

stefanbeller, I haven't checked if this happens in 0.8, but since plangoworthy mentioned that something similar/same happens, I'm sure it will.

[plangworthy]

Most of the times the cursor is completely absent when I first switch to a "broken" map without doing anything. If I start dragging the mouse around, the cursor will start to appear.

I can get lots of strange behaviors if I start sampling tiles. For example, let's say that I right click and drag- the selection tool will actually work pretty much correctly. After I release the button, I'll see the highlighted selection and preview tiles centered on wherever the mouse was when I released, but the selection will not follow my mouse around. It's just stuck where ever it originated. If I click the mouse at this point, it will place the tiles, but wherever the brush is stuck, not where I clicked. If I drag at this point, it will start placing the tiles where my cursor is (correctly). However, when I release the mouse button again, the cursor gets "stuck" wherever I released. The next time I click, regardless of where I click, that stuck spot is where the first tiles will get placed. If I just keep clicking and don't drag, then the brush never moves. Only once I start dragging does the brush position seem to get updated correctly.

Basically, it seems as though during any kind of dragging event, the cursor position updates correctly, but during any other time there is no position updating going on for the mouse.

Randomly, I've found that there is some kind of sequence of events (switching maps and clicking about) that will "fix" the problem for the rest of the session.

I should sat that I definitely see some truth to the notion that it has to do with switching between maps with different aspect ratios. For example, to a map that is taller than it is wide from a map that is wider than it is tall (or vice-versa). I can usually switch between maps that share a common aspect ratio during a single session and the cursor will continue to operate correctly. I didn't notice this before because most of my maps have different aspect ratios so it always seemed to be happening.

[exactspace]

Yes, what you described seems like the same thing that is happening to me! I usually just test to see if it's happening on a current tab, and if it is, I close the tab and open the file again and it's fine.