XML problems

[DR BILRO]

considering the following xml example

<?xml version="1.0" encoding="ISO88 59-1"?>

<results>
<interaction>
<point>
<auxf>6.81289 0</auxf>
<auxh>0.00000 0</auxh>
</point>
<point>
<auxf>5.61415 7</auxf>
<auxh>0.47975 7</auxh>
</point>
<point>
<auxf>4.04000 0</auxf>
<auxh>38.000000 </auxh>
</point>
</interaction>
<interaction>
<point>
<auxf>6.81289 0</auxf>
<auxh>0.00000 0</auxh>
</point>
<point>
<auxf>5.61415 7</auxf>
<auxh>0.47975 7</auxh>
</point>
</interaction>
</results>

how can i get the diferent points for each interaction?
i i'm seeing the first interaction i would get access to 3 points, otherwise
i get access to two points

i can only get all the points of all interactions

--
To me or not to me

[Derek Harmon]

"DR BILRO" <DR*****@discus sions.microsoft .com> wrote in message news:03******** *************** ***********@mic rosoft.com...

how can i get the diferent points for each interaction?
i i'm seeing the first interaction i would get access to 3 points, otherwise
i get access to two points

i can only get all the points of all interactions

What you must be doing is using the // (descendents-or-self) axis in an
XPath expression selecting all <point> elements. There's a DOM node
tree underneath, it would probably be a better approach to go to each
<interaction> element individually, and then select only it's <point>
elements.

- - - interactions.cs
using System;
using System.Xml;

public class App
{
public static void Main()
{
XmlDocument xmlDoc = new XmlDocument();
xmlDoc.Load( "points.xml ");

XmlNode eResults = xmlDoc.Document Element;
XmlNodeList nodes = eResults.Select Nodes( "interactio n");

// Getting the atomic strings from the NameTable allows you to
// do comparisons against the names of the elements more
// efficiently.
//
string atomAuxf = xmlDoc.NameTabl e.Get( "auxf");
string atomAuxh = xmlDoc.NameTabl e.Get( "auxh");

if ( nodes != null )
{
foreach( XmlNode eInteraction in nodes )
{
XmlNodeList nodesInner = eInteraction.Se lectNodes( "point");
if ( nodesInner != null )
{
foreach( XmlNode ePoint in nodesInner )
{
// If you see NaN displayed, then the FirstChild / LastChild
// simplification may not apply and you require additional
// logic below.
//
double auxf = double.NaN, auxh = double.NaN;

XmlNode eAuxf = ePoint.FirstChi ld;
XmlNode eAuxh = ePoint.LastChil d;

// Make sure it's an Element, that it's <auxf> (or <auxh>),
// and then convert it's first child (which had better be a
// XmlTextNode) to a double.
//
if ( eAuxf.NodeType == XmlNodeType.Ele ment )
if ( eAuxf.LocalName == atomAuxf )
auxf = Convert.ToDoubl e( eAuxf.FirstChil d.Value);

if ( eAuxh.NodeType == XmlNodeType.Ele ment )
if ( eAuxh.LocalName == atomAuxh )
auxh = Convert.ToDoubl e( eAuxh.FirstChil d.Value);

Console.WriteLi ne( "Point ( auxf={0}, auxh={1} )", auxf, auxh);
}
Console.WriteLi ne( );
}
}
}
}
}
- - -

What sort of processing you want to do on these <point> elements is
entirely up to you, in this example I've just displayed them to the console
window.

I will point out that I make use of a few simplifying assumptions, namely:

1. The auxf is always the FirstChild of point.
2. The auxh is always the LastChild of point.
3. The auxf and auxh always contain a normalized XmlTextNode as their
First (only) Child that's parseable as a Double w/o causing a Format-
Exception.

In a real-world application you'll need to apply additional checks ensuring
these pre-conditions are valid. In particular, it's possible for a Comment,
for example, to exist between auxf and point and that would disrupt these
assumptions. Normally, you'll want to write code that starts with the
FirstChild and then use it's NextSibling to iterate through the child nodes
looking for the ones you want (checking if they are XmlNodeType.Ele ment
and then checking their LocalName against one of the atomized tag
names).
Derek Harmon

[Derek Harmon]

"DR BILRO" <DR*****@discus sions.microsoft .com> wrote in message news:D1******** *************** ***********@mic rosoft.com...

Public Function numInter() As Integer
Dim num As Integer
Dim myTable As DataTable
Dim myRow As DataRow
num = 0
myTable = DataSetResultad o.Tables("inter action")
For Each myRow In myTable.Rows
num += 1
Next myRow
Return num
End Function

This Function could be simplified as,
Public Function numIter( ) As Integer
Return DataSetResultad o.Tables( "interaction"). Rows.Count
End Function
Are there any other advantages to DataSet in your application
(are you data-binding to any Controls?)

If the DataSets are not required, XmlDocument would probably
be more flexible and in-line with the earlier solution I've posted.

A third option is an XmlTextReader subclass, that's the most
efficient, but because the implementation details of using an
XmlReader to parse an XML document may obscure the main
points of this solution, I'll exclude describing it.

I've translated the solution I posted in C# to VB.NET, and
show the while-loop I described as being more robust that
enumerates all of the child nodes (in the event there were
ever more than auxf and auxh).

- - - InteractionsApp .vb
Imports System
Imports System.Xml

Public Class InteractionsApp

Public Shared Sub Main( )
Dim xmlDoc As New XmlDocument( )
xmlDoc.Load( "resultado_fina l.rst")

Dim eResults As XmlNode
eResults = xmlDoc.Document Element

Dim nodes As XmlNodeList
nodes = eResults.Select Nodes( "interactio n")

Dim atomAuxf As String = xmlDoc.NameTabl e.Get( "auxf")
Dim atomAuxh As String = xmlDoc.NameTabl e.Get( "auxh")

If ( Not nodes Is Nothing ) Then
Console.WriteLi ne( "Number of Interactions = " + CStr( nodes.Count) )
For Each eInteraction As XmlNode In nodes
Dim nodesInner As XmlNodeList
nodesInner = eInteraction.Se lectNodes( "point")

If ( Not nodesInner Is Nothing ) Then
For Each ePoint As XmlNode In nodesInner
Dim eChild As XmlNode = ePoint.FirstChi ld
Dim auxf As Double = Double.NaN
Dim auxh As Double = Double.NaN

While ( Not eChild Is Nothing )
If ( eChild.NodeType = XmlNodeType.Ele ment ) Then
If ( eChild.LocalNam e = atomAuxf ) Then
auxf = CDbl( eChild.FirstChi ld.Value)
Else If ( eChild.LocalNam e = atomAuxh ) Then
auxh = CDbl( eChild.FirstChi ld.Value)
End If
End If
eChild = eChild.NextSibl ing
End While
Console.WriteLi ne( "Point ( auxf={0}, auxh={1} )", auxf, auxh)
Next
Console.WriteLi ne
End If
Next
End If

End Sub

End Class
- - -
Derek Harmon

[DR BILRO]

it was perfect. soberb!!

instead to send it to the cosole i added to a array of PointF and then i can
work easily with the points.

now i have the point ready.
the hard part : i need to show them.

i need to draw a chart like it's done in Excel but on my on.
each point connects to the following (if any), but how can i do the axis

something like this:

| P2
3-|......x
| . P1
|.............. ............... ............... .x
| . .

|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----
1.2 1.3 1.7 2.5
16.3

can you help me? urgent.