Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Scroll to region info when selecting a region

A topic by Kornalius created Mar 19, 2022 Views: 299 Replies: 12
Viewing posts 1 to 13

When selecting a region in the spritesheet, it would be nice to select and scroll to the Regions information. I have a spritesheet with over 500 regions and it's really hard to find the region name etc...

Thanks

Developer

Hello and thank you for the bringing this up.

Could you please describe the exact steps to reproduce your issue and also a desired result?
Also it would be helpful if you add your OS version to the report.

I have checked with the current app version and whenever I select a region inside spritesheet, the panel on the right scrolls to the corresponding region data piece.

I've done it like this:

1. File -> New

2. Load Image ( I've used a random .png of 296x194)

3. I set a grid with cell dimensions of 10x10 pixels

4. I created 551 regions using the button "From grid"

5. I tried selecting different regions with the left mouse button and  each time the data panel on the right scrolled automatically to an appropriate data set.


Maybe I misunderstood you about the nature of your problem, so, it would be nice if you could elaborate.
Thanks.

How do select the regions on the left? Just the left mouse button does not do anything for me. I am running on linux.

Developer

Hello.

Sorry for the delay.
Region selection works identically both on Linux and Windows platforms: you just left-click on regions in your working area.

I will investigate and try to reproduce this bug on my Linux system.

Can you supply more details about your installation?
Like distro version, kernel version, desktop environment, virtual machine/native installation and so on?

Developer

For now I've managed to check the issue on my VM installation of Linux Mint 19 Tara x86_64 with the Atlased 1.1.1a and could not reproduce it.

Also, people using Manjaro x64 (rolling) reported back to me that they didn't encounter something like this. 

So seeing any details on exact repro steps, system version(s) and so on would be really helpful.

I am not at home but I will try to provide a video and more info about my system shortly.

Here are my system information:

 OS: Ubuntu 20.04 focal
Kernel: x86_64 Linux 5.4.0-105-generic
Shell: fish 3.1.0
Resolution: 3840x1200
DE: GNOME 3.36.5
WM: i3
Disk: 373G / 481G (82%)
CPU: Intel Core i7-6770HQ @ 8x 3.5GHz [70.0°C]
GPU: Mesa Intel(R) Iris(R) Pro Graphics 580 (SKL GT4)
RAM: 14398MiB / 32001MiB

And here is a little video that shows that simply clicking a region on the left does not work for me. Btw, I am using v1.1.1a. I have to click and drag but it still does not focus to the region data on the right.

Here is a little video (it's on Dropbox since I cannot embed large files in this post, I hope it works)

Atlased.gif

Developer (1 edit)

Thanks for the update. Sorry for drastic delays. I'll try to reproduce this bug and come up with solutions, if any, as soon as I have time and energy for that.

Have you tried to reproduce the issue in non-tiling windows manager? And just a wild guess: do you have any version of qt runtime installed? If so, which one?

(1 edit)

Thanks for you reply.

As per dpkg -l | grep Qt, I seem to have version 5.12.8 of the Qt5 library installed.

Oddly enough, if I start from scratch again with the same base spritesheet, select 'From Grid', I can easily select with the left mouse button.

Comparing the two files, I noticed that my original file has "height": 64 while the new file has "height": 928, which is the correct height for the spritesheet image. So it looks like somehow the file height was mis-calculated or something. The "width" was also set to 64 when it should be 256 pixels.

I wonder if changing the grid size caused this issue somehow?

This is definitly the problem, as I can select regions with the mouse for the first 4 rows only (64 pixels).

Developer

I've tested the app on Linux Mint 20.03 with i3 wm and I could not reproduce the issue.

The things you're saying about your file's geometry being malformed are disturbing yes, but I can't determine the reason behind such behavior.

I've rechecked the code and image geometry is set only during the loading process directly from  image file, there's no any 'calculation' step involved (aside from possible PNG loading code inside Qt).

Also, changing the grid size does not affect atlas or image dimensions.

Existing atlases loader seems to be doing fine too.

I'm sorry to hear about your troubles, but so far I could only theorize that your image somehow became "incompatible", which caused a glitch within PNG loader, but this is just another wild guess - I've tested the app with many PNGs from various sources (pinterest, twitter, Adobe Photoshop, GIMP, Krita, Aseprite). Or the issue could be caused by an unlikely bug inside Qt loader (has nothing to do with your system version).

If this issue will occur again, I suggest working around by editing atlas' JSON file - it's fields "width" and "height", as inconvenient as it is.

Or we could pursue 100% reproduction angle with detailed repro-steps. If you manage to find out how to make this issue appear consistently, it would be much appreciated, because then I will be able to fix it.

Thanks.

I think the reason is because the file size keeps on growing as I add more sprites to it. This seems to be normal behavior when you think about it. Unless you make your code update the dimensions in the JSON file has the image file is loaded, I don't see how you can resolve this issue otherwise.

Now that I know how I can fix the issue manualy I wouldn't worry about it too much.

Best Regards,

Alain

Developer

Oh, I see.

That's a good point, and that could be a feature update sometime in the future. Never thought about such a use case, honestly :)

So, to clarify: you modify your sprite sheet in graphics editor and then trying to add more markup to it within an already existing JSON atlas?

Thanks.

Yes, I keep on adding sprites to the sheet, it grows, then I simply reload the file in Atlased (same JSON) and I mark new regions, but since the sizes have changed, I cannot click on areas outside the previous image sizes.