Macro Library not scrolling correctly and more

[Rick G]

I am working with the Photo beta 16.0.82 on Windows 10 x64

This is not an issue in PHOTO 1.52.69

I just imported a few macros into the library

I could not view them all

The scroll bar does not work (you cannot grasp it with the mouse pointer) and the arrows go either to the top or bottom

My work around was to make additional categories and have less that 13 in each category as any attempt to scroll seems to jump categories

If someone could test that and if I am missing something please advise

Thanks

Edited September 24, 2017 by Rick G
Better information

[affwin]

Hi Rick G, yes this is indeed so. No scrolling possible in the Marco library. Is a bug.
Nice that you have reported this.
Greeting Dieter

[Alfred]

I can scroll by clicking below (or above) the scrollbar button, but not by dragging on it. When I move the button away from the top of the track, it shrinks to half of its original length.

 

The arrows work as expected here.

 

[Rick G]

39 minutes ago, Alfred said:

I can scroll by clicking below (or above) the scrollbar button, but not by dragging on it. When I move the button away from the top of the track, it shrinks to half of its original length.

 

The arrows work as expected here.

 

Yes clicking the column will make the scroll bar jump. Clicking the top and bottom scroll arrows does the same thing. It appears to jump categories. Shrink the box down a bit and you will see you cannot get to all the macros on the list. If you make the library full height and limit yourself to 10 macros per category, you can get to them

Thanks for the quick response

[Alfred]

Just now, Rick G said:

Yes clicking the column will make the scroll bar jump. Clicking the top and bottom scroll arrows does the same thing.

 

I had originally thought that the arrows were behaving as expected, but looking again I can confirm that it's as if I'm clicking on the scroll track.

 

[Sean P]

Reproduced here, will get it reported to development.

Thanks for letting us know

[Rick G]

Still broken in beta 1.6.0.83

[Sean P]

Morning Rick! Please try to be patient with fixes. I posted stating that I had reproduced and reported the bug to development at 08:38 Monday morning, build 83 then came along 3 hours later at 11:39.

It takes a bit longer than 3 hours to get an issue fixed and in a build. In fact we already had build 83 internally prior to you reporting the issue! Please do keep an eye on the fix list - if you notice the fix being listed on that and still find it broken then by all means let us know. If you don't see the fix listed, it is unlikely it will have been fixed.
 

[Rick G]

I am not impatient at all. I am sorry if it sounded that way. I am just following bugs and marking them. It is more for the next user and hopefully will reduce posts. If anyone else is following

I was just following up with it, You will get to it as you will. No complaints here

[Rick G]

Fixed in 1.6.0.84

Thanks!