Skip to Content
author's profile photo Former Member
Former Member

UIAPI indicate selected row in Matrix

Hi all,

here is another question with no answer to it yet.

We are still working with version 6.2.

As far as I know there are (at least) two known problems with the matrix object

a) there is no "selected row" property returning a row object - this can be dealt with by using the pval.row property and adressing the different row columns directly

b) in 6.2 the selection of a row can not indicated by a change of color

Regarding the color change:

If a user clicks on a row in 6.2, is there any way to mark the row as selected? Not necessarily a colorchange, any workaround will do.

I have tested the following:

-add another column of type checkbox

-on Click event uncheck the checkbox in previous row and check the one in the current row

This looks promising, but still does not work 100%.

Any other propositions for a workaround?

TIA Lutz Morrien

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jun 20, 2004 at 08:55 PM

    Just to let people know:

    I did manage to use checkboxes in a matrix in order to indicate a selected row in a version 6.20 matrix. It is kind of clumsy as a workaround and does not look too SAP, but it does work. If anyone needs this workaround, I can post some code.

    Lutz Morrien

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      the BlockEvents method is self made. (I simply forgot to take it out I guess).

      It exists in the topmost class which is connected to SAP via UIApi. If I set blockEvents to true, this class blocks off all events the class gets from SAP until I finish an action. It just does not hand them down to other classes.

      If I perform an action, I get a number of events until the action is complete. If I know that my application does not need to handle these events, I block all events at top level until the action has been completed.

      It is not a SAP built function.

      I know about the flaws in 6.2 and I really do not get along too well with it. However, our customers are not upgrading yet and therefore I am stuck with 6.2 ;(

      The fact that one cannot run a 6.2 and 6.5 client on the same machine does not help either.

      Lutz Morrien

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.