Skip to Content
author's profile photo Hideyuki Amari
0
Hideyuki Amari

How to display Context structure without using Table and Tree control?

Posted on Jun 02, 2004 at 08:46 AM 14 Views

Hello WD dynamic programming expert,

I want to display elements under one Node simultaneously using InputField.

Do you know how to do this?

I assigned the InputField to Context-Attribute.

I thought I can bind Context-Attribute with index, but it couldn't.

(I tried to bind like "Orders.OrderNumber[1]")

================================================================

My Context Structure is like this:

<Root>

<Orders> (cardinality 0..n)

OrderNumber

<Items>

ItemNumber

ItemText

And I want to display like this;

----

----

+

.OrderNumber..[ 1001].

.Item1.[ mat1].[ NoteBook ].

----

.Item2.[ mat2].[ Pen ]......|

......................

.Item3......................

|......................----

|....................................................

----

----

+

.OrderNumber..[ 1002].

.Item1.[ mat5].[ PC ].......

----

.Item2.[ mat8].[ Box ]......|

......................

.Item3......................

|......................----

|....................................................

----

----

+

.OrderNumber..[ 1003].

.Item1.[ mat5].[ PC ].......

----

.Item2.[ mat2].[ Pen ]......|

......................

.Item3......................

|......................----

|....................................................

.....(iterating)

**Please display with non-propotional fonts

====================================================================

My View Structure is

<RootUIElementContainer>

<Group> -

dynamically added element

<InputField> OrderNumber is binded Orders.OrderNumber

<Table>

<InputField> ItemNumber is binded Orders.Items.ItemNumber

<InputField> ItemText is binded Orders.Items.ItemText

</Table>

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 02, 2004 at 01:14 PM
    0

    Hi Hideyuki,

    Is there any reason, why you do not want to use a table for this structure?

    Regarding your question:

    You can not bind an InputField against a specific node element, you can only bind it against the one you chose via leadSelection.

    So, you have two possibilities: you can either use a table ui element for that, which is THE ui element for displaying orders, if you want to see all at once please check out Table.visibleRowCount = -1.

    Or you need to change your complete context structure. If you create one InputField for each context attribute, it should work.

    We would recommend the table, anyhow!

    Hope that helps!

    Karin

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 02, 2004 at 05:01 PM
    0

    Hi Hideyuki,

    it's easier than you thought, use node.index instead of node.[index] so in your case "Orders.OrderNumber.1". The path is resolved in a trial and error procedure, each path part which doesn't throw a number format exception if converted to an int is used as an element index. But i'm not quite sure if this works for binding also. Have a try! By the way (like Karin already said), does this really make sense?

    Hope that helps.

    Regards

    Stefan

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Hideyuki Amari
      Jun 03, 2004 at 06:24 PM

      Hi Hideyuki,

      the idea with the Web Dynpro Component at the end is not bad. I would suggest to create a component which contains (at least) the view displaying the details. In the component "owning" the table, create two component usages with different names, but using the same detail component. Place the interface views of the component usages in a ViewSet or two ViewContainerUIElements for example. When the "Display 2 orders..." button is pressed, "feed" the used detail components with the selected entries.

      Hope that helps.

      Regards

      Stefan

    Comment on This Answer

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.