Skip to content

Conversation

@deathbeam
Copy link
Contributor

  • Properly create undo state while 100% preserving same indices
    (probably unnecessary but I noticed that I was relying on ordered
    index)
  • Move getting displayId from displayGroup at start of restore undo
    method (like before) so it can get the position before the values are
    replaced and instance comparison is no longer possible. Without this
    change display group always resets on undo

Signed-off-by: Tomas Slusny slusnucky@gmail.com

Steps to reproduce

  • Add random gem to new socket group
  • Add another random gem
  • Undo
  • Display group is reset

This PR fixes the last part.

- Properly create undo state while 100% preserving same indices
  (probably unnecessary but I noticed that I was relying on ordered
  index)
- Move getting displayId from displayGroup at start of restore undo
  method (like before) so it can get the position before the values are
  replaced and instance comparison is no longer possible. Without this
  change display group always resets on undo

Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
@QuickStick123 QuickStick123 added the bug Something isn't working label Jul 11, 2022
@Wires77 Wires77 merged commit c82dd58 into PathOfBuildingCommunity:dev Jul 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants