Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't select map tiles or edit their properties #1829

Closed
chriscamacho opened this issue Dec 6, 2017 · 14 comments
Closed

Can't select map tiles or edit their properties #1829

chriscamacho opened this issue Dec 6, 2017 · 14 comments
Labels
usability Generally about making something more intuitive or efficient.

Comments

@chriscamacho
Copy link

chriscamacho commented Dec 6, 2017

I using something a version I pulled from git today (default? branch?)

I have a single layer map of tiles, in the tile set editor I have given some tiles custom properties, and indeed when selecting these tiles to add to the map I see the greyed out properties for these tiles

However there seems to be no intuitive way to select an existing tile on the map so I can edit its properties, I've even used the rectangle tool to carefully select just one tool!

at all times the properties view is greyed out, having tried every option I can think of this is either a bug or something so unintuitive it is an issue! (I didn't have this issue last project I used it but then the UI looks like its had a radical makeover!)

the select object button is always greyed out but then tiles and objects are different afaik ?

The tile set is not embedded in case this makes a difference (and I'd prefer to keep them separate as the end use is to place 3d objects on a plane (with properties but without the tile graphic!) which is working really well!

@bjorn bjorn added the usability Generally about making something more intuitive or efficient. label Dec 6, 2017
@bjorn
Copy link
Member

bjorn commented Dec 6, 2017

Yeah, this is a new issue since Tiled 1.0 (before this version, you could directly change things affecting tilesets (which includes tile properties), as long as they were embedded). It is related to issue #822, which I recently reopened.

The reason you can't edit those tile properties while editing the map is the undo stack. The tileset has its own undo stack, so actions that modify the tileset should go there. Switching to the tileset is necessary to make it clear which undo stack you're operating on.

But it is clear we need to restore quick access to those tile properties for better usability. I think the question is what should we do with the undo system?

@chriscamacho
Copy link
Author

I'm sorry, what???

specifically what do I need to do to edit tiles on the map, how does one switch to the tileset ?, I only have one tileset!

@bjorn
Copy link
Member

bjorn commented Dec 6, 2017

You switch to the tileset by opening its file, or by clicking the "Edit Tileset" button below the tileset view.

@chriscamacho
Copy link
Author

its been open all along - no difference

@chriscamacho
Copy link
Author

reverted back to 0.18.1 still doing the same thing,

@bjorn
Copy link
Member

bjorn commented Dec 6, 2017

Did you read this part of the manual? http://doc.mapeditor.org/en/latest/manual/editing-tilesets/

If you're still confused, please try to show a screenshot, because I don't understand what isn't clear. Once you have opened the tileset, and click on a tile, you are able to edit its properties.

@chriscamacho
Copy link
Author

chriscamacho commented Dec 6, 2017

I think we both misunderstood each other! I want to change the property for a tile on the map
I can do this by adding a tile to an object layer but its too easy to inadvertently make stacks of tiles (on the same grid square) when snapping to grid, which would make my physics explode!

to be clear I would like to be able to have one tile on the map with different values to other tiles (of the same type) in a custom property (like I can in an object layer)

@bjorn
Copy link
Member

bjorn commented Dec 10, 2017

@chriscamacho Ah, sorry about that! It seemed to me you were rather reporting an issue than requesting a feature. Other than using objects there is no way to associate properties with locations. See issue #31 for a discussion about that.

In case you are marking collision tiles, you probably have only a limited number of values for your custom property. In that case, you could create a special tileset and use it on a "collision layer", which would be more comfortable than fiddling with local tile properties. Of course this may not fit your use-case, anyway.

@bjorn bjorn closed this as completed Dec 10, 2017
@chriscamacho
Copy link
Author

I just assumed tiles could have any property needed, looks not, I need a number of properties, I'll have a look...

@RichardJECooke
Copy link

Sorry, I'm still confused by this.
Are we saying that tiles in maps can have properties, but there's just no way to edit them?
Or are we saying only tile in sets can have properties and tiles in maps can't?

@bjorn
Copy link
Member

bjorn commented Mar 15, 2021

@RichardJECooke Tiles in a tileset can have custom properties. A tile layer just refers to those tiles, so there is no way to set custom properties on just some of those tile references. If you need location-sensitive custom properties, you need to use an object layer, and set those custom properties on an object.

Of course, this object could be a tile object, in which case you can associate custom properties with just that instance of the tile.

@chriscamacho
Copy link
Author

The though just occurred to me if there was an optional snap to grid option (be in square, iso or hex) then that could add a fair bit of flexibility to maps...

@bjorn
Copy link
Member

bjorn commented Mar 15, 2021

@chriscamacho There is an optional Snap to Grid option:

image

@chriscamacho
Copy link
Author

chriscamacho commented Mar 15, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usability Generally about making something more intuitive or efficient.
Projects
None yet
Development

No branches or pull requests

3 participants