[50940] in SAPr3-news
TableControl issue...
daemon@ATHENA.MIT.EDU (Ivaylo Mutafchiev)
Wed Aug 4 05:00:42 2004
To: sapr3-news@mit.edu
Date: Wed, 4 Aug 2004 12:00:32 +0300
From: "Ivaylo Mutafchiev" <ism_NoSpamPlease@mail.bg>
Message-ID: <2nbmtjFsvcstU1@uni-berlin.de>
Hi,
I've implemented own table-control (using GUI screens) which visualize some
internal table. The (normal) behaviour is when some line is selected,
previously selected one is un-selected first. Everything is fine if I deal
with rows on 1st screen (assume my IT is large and there are several pages
of it). I found, that when I press page-down, or go to some other page using
scroll-bar and select some row, then previously selected row on my 1st (or
whatever previously shown) page is still selected - so I have 2 or more
selected rows - which broke my logic further.
My question is: how to deal with previously selected row in such situation
in order ot prevent incorrect behaviour?
Any hint would be highly appreciated.
TIA
Ivaylo
P.S. A little snip of code below:
PROCESS AFTER INPUT.
...
LOOP AT logHead.
FIELD logHead-selected MODULE tbllog_mark ON REQUEST.
ENDLOOP.
...
MODULE tbllog_mark INPUT.
MODIFY logHead FROM logHead
INDEX tbllog-current_line TRANSPORTING selected.
ENDMODULE.
