-
Notifications
You must be signed in to change notification settings - Fork 293
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
Spritesheets are re-published after merely selecting them #736
Comments
I cannot reproduce this on develop (2201c04) nor on 1.1 (App Store version). Did you select Release for publishing? My steps:
|
Try it with the LearnSpriteBuilder project here: I have develop mode selected in SB but I'm building the release configuration in Xcode. I can definitely reproduce it just by clicking on the spritesheets in the SpriteSheets folder. Edit: also happens when I build debug config in Xcode, so that's not it. |
Like I said, you have to select the spritesheet (folder) itself. Selecting images contained in the folder does not cause the issue. P If you have just one spritesheet, be sure to select a different folder, then publish, then select the spritesheet folder again, and publish again to see if just clicking on the spritesheet causes a re-publish. Though for me the following does provoke a re-publish so it may not be necessary to select something outside the spritesheet:
|
Also noticed that the re-publish occurs on the Tileless Editor View tab. Merely checking and unchecking the sprite sheet in the Filter Folders section at the bottom of the view causes a re-publish. This occurs for both checking and unchecking the sprite sheet. |
…d it as dirty. This lead to redundant publishing passes.
…e_marks_them_as_dirty Bugfix/#736 selecting resource marks them as dirty
Every time I simply click on a Spritesheet folder, SB will re-publish that particular spritesheet. Apparently merely the act of selecting the spritesheet folder flags the spritesheet as "dirty".
Note: selecting one of the images contained in the spritesheet does not cause a re-publish.
The text was updated successfully, but these errors were encountered: