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

Desired Size of Objects Not Considered #449

Closed
cemalgnlts opened this issue Aug 3, 2023 · 1 comment · Fixed by #450
Closed

Desired Size of Objects Not Considered #449

cemalgnlts opened this issue Aug 3, 2023 · 1 comment · Fixed by #450
Labels

Comments

@cemalgnlts
Copy link

Context

I have a 64x64 map, but the objects are larger than these dimensions.
I can change the size of the object after adding it to the map:
Screenshot 2023-08-03 15 24 56
(In the picture, I changed the Width and Height values of the object to 64x64 to fit the map.)

This size is recorded in the *.tmx file as follows:

<objectgroup id="3" name="Objects">
  <properties>
   <property name="excalibur" type="bool" value="true"/>
  </properties>
  <!-- I edited the dimensions of this object. -->
  <object id="8" name="doorIn" gid="32" x="120.095" y="256.191" width="64" height="64"/>
  <object id="9" name="doorOut" gid="37" x="440.15" y="256.812" width="64" height="64"/>
  <!-- The width and height values of this object are as they should be. -->
  <object id="10" name="doorOut" gid="37" x="440.15" y="256.812" width="78" height="96"/>
</objectgroup>

But this change is being ignored.

Proposal

The sprite that the object points to should be found by gid and if the width and height values are not the same, it should take the width and height values that the object has.

@eonarheim eonarheim added the bug label Aug 3, 2023
@eonarheim
Copy link
Member

@cemalgnlts Thanks for the issue, I agree the plugin should respect this!

Shouldn't be a tough thing to fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants