2007 May 15 6:58 PM
I have an ALV grid in a custom container that's sized for a screen on a high-resolution tube. In other words, there's a scrollbar on the ALV but none on the screen itself (because the whole screen is visible at the high resolution.)
At this high resolution, a find or find next will correctly scroll the ALV to the row in which an item is found (when the "found" row is below the currently visible row of the ALV.)
But when I switch to a lower resolution where I have a scroll bar on the ALV and on the window itself, a find or find next does not scroll the ALV properly. You have to manually scroll to find the found row.
Yes - I have both resizings checked on the container.
Is there a way I can:
1) find the resolution the user is in?
2) modify the screen size to fit this resolution?
3) modify the container size to fit this resolution?
Thanks
djh
2007 May 15 7:37 PM
Hi David,
If your container was placed on a screen painter , you can easily expand the screen to max . values that i could have .
And you can set the custom control attributes: check the box for resizing vertical, horizontal and set the minimum lines and minimum columns to 1.
Hope this will be useful
Regards
Caglar
2007 May 15 8:11 PM
Calgar -
This is the same thing that Thomas (Jung) suggested in an old ABAP General thread.
But I've done it, and it doesn't work.
Also, I don't understand why I'm getting a scroll bar for the ALV as well as for the screen.
I thought if I did what you and Thomas said, I would only see the scroll bar for the screen and not the ALV.
Any other ideas ????
Thanks
djh
2007 May 15 9:21 PM
Calgar - I've given you 6 for responding even though the problem was something else entirely.
If you have a custom subscreen on top of the alv, the resizing gets screwed up !!!!!
As soon as I commented out the call to the subscreen in the flow logic, the problem disappeared.
2007 May 16 2:05 PM
Hi David,
It is nice to hear that your problem is solved.
By the way thanks for the points...
Regards .
Caglar
2007 May 17 8:26 PM
Sounds like a GUI error. Make sure you have the latest patches for your SAP GUI.
2007 May 17 8:46 PM