Page 1 of 1

Library Viewer and identifying data better

Posted: Sun Apr 16, 2023 2:02 am
by BarryG
My app uses a lot of images (over 600), some created with constant names from Enumerations, and some created during runtime with #PB_Any. However, the Library Viewer only shows them by their internal numbers:

Image

This makes it really hard to find an image that I need to see, such as #Img_Icon_Today, because I have no idea what number was given to that constant with Enumeration. So I need to sit there and repeatedly cursor down the list until I find it visually.

My request is obvious: can the Library Viewer show any relevant constant names as well (maybe a "Constant" column)? Or better identifying info?

The same goes for windows, too. Showing a window's constant name would be helpful, and even showing a thumbnail of the window's image when you click it in the viewer would be nice (like it does for images).

Thanks!

Re: Library Viewer and identifying data better

Posted: Sun Apr 16, 2023 10:42 am
by luis
BarryG wrote: Sun Apr 16, 2023 2:02 am This makes it really hard to find an image that I need to see, such as #Img_Icon_Today, because I have no idea what number was given to that constant with Enumeration. So I need to sit there and repeatedly cursor down the list until I find it visually.
If you hover with the mouse on the constant name you can see its value.

Re: Library Viewer and identifying data better

Posted: Sun Apr 16, 2023 12:39 pm
by BarryG
But then I have to open the source file where it is, and scroll to it just to hover... I have over 60,000 lines in my expanded source. So if I'm at line 40,000 and need to scroll back to somewhere around line 20,000 just to find a constant... it's not fun. There has to be a better way. Even just sorting the image list in the Library Viewer from newest to oldest would help, because then I'd only need to arrow down the last few images because the image was recently created.

Re: Library Viewer and identifying data better

Posted: Fri Sep 13, 2024 7:14 am
by Randy Walker
BarryG wrote: Sun Apr 16, 2023 12:39 pm I have over 60,000 lines in my expanded source. So if I'm at line 40,000 and need to scroll back to somewhere around line 20,000 just to find a constant... it's not fun. There has to be a better way.
Wow!! 60k lines is a huge project (in my mind). If you know it's around line 20k, can't you use Ctrl G to jump there rather than "scroll back"? I run into similar issues myself. (My project is up over 28k now and I thought 20k lines was huge.)