You should call these super class methods towards the end of the processing in method GET_DATA
, so that:
In method ADJUST_FIRST_VISIBLE_ROW
the selected entry in the list is visible in the LIST UIBB.
It can sometimes occur that if the list is longer than the viewing pane allows and the user must scroll through it, the user selects
the Next
button, and the line selected is off the bottom of the part of the list currently shown. The correct pay slip is shown, but the user cannot see the selected period in the list.
The method adjusts the list so that the selected period is visible in the viewing pane.
In Method HANDLE_PREVIOUS_NEXT_ACTIVATION
the buttons Previous
and Next
on the screen are set to inactive or active. This depends on if after the current event has finished processing there
actually is a previous or next entry in the List.
If not, the buttons are greyed out.
Just call these super methods to get this handling.
Example
Code example for handling button activation:
Syntax
IF mv_prev_lead_index NE cv_lead_index
OR lv_prev_tab_lines NE lines( lt_data> ).
cv_first_visible_row = me->adjust_first_visible_row(
iv_lead_index = cv_lead_index
iv_first_visible_row = cv_first_visible_row
iv_visible_rows = iv_visible_rows
iv_max_index = lines( lt_data> )
if visible_row should be set according on max. shown entries use:
iv_max_index = lines( mt_filtered_rgdir )
).
me->handle_prev_next_activation(
iv_lead_index = cv_lead_index
prev/next only on actual shown entries possible
iv_max_index = lines( lt_data> )
if prev/next should be set according on max. shown entries use:
iv_max_index = lines( mt_filtered_rgdir )
mv_prev_lead_index = cv_lead_index
ENDIF.