Hi
I was wondering if anyone else has used XML in D6 and was as
'indecisive' as I am, I've looked at 2 imps (TXMLDocument - std D6 and
ICom TicXMLParser) They both seem to have their advantages
1/ TXMLDocument, Nice DOM with interfaces, but requires MS or IBM XML
2/ TicXMLParser, Not so nice DOM
Hi all
I'm scratching my head
NodeAttributes['Att'] := 10 sets Att="10" even tho 10 is an integer
Does anyone know how to set an 'unquoted attribute ie Att=10
TIA
Regards Neven
N.K. MacEwan B.E. E&E
Ph 649 574 0027
Fax 649 570 2706
[EMAIL PROTECTED]
---
Hi
I was wondering if anyone else has used XML in D6 and was as
'indecisive' as I am, I've looked at 2 imps (TXMLDocument - std D6 and
ICom TicXMLParser) They both seem to have their advantages
1/ TXMLDocument, Nice DOM with interfaces, but requires MS or IBM XML
2/ TicXMLParser, Not so nice DOM
Unfortunate according to the latest XML standards, all attributes should be
quoted. The parsers supporting parsing in unquoted strings for historical(?)
reasons. :-(
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Neven MacEwan
Sent: Thursday, October 18,
For deployment reasons, I decided not to use the MS parser but use the
Delphi Open Source parser from Dieter Kohler at
http://www.philo.de
Good DOM, quick, a bit monolithic inside.
Nowhere near as sexy as the graphical XML tools in D6 but then I'm still on
D5.
-Original Message-
From:
The unquoted value is _illegal_ in XML. You can't do it. You specify the
_type_ of the variable in the XSD (XML Schema Defn) - with "our" XML parser
/ wrapper, it generated interfaces for you - as you know- and manages the
types for you in there.
bottom line: no XML parser should handle this
N
Nic
Thanks, My XML book was a little old, 1999!
I like the TXMLDocument and using it has certain adavantages (like the
wizard support)
but it would be nice if some bolted one of these 'native' delphi parsers
onto it,
So it didn't required the MS or IBM XML parser
Neven
- Original Message -
I have an
application which is causing me trouble, but I am at a loss as to how to debug
it.
I need to describe
the application and how it works, so that you can understans my problems so here
goes:
Its a data
viewing/editing application for the roading industry.
There is a list of
roa
Are you calling Free (rather than Destroy) to
destroy the forms?
Bob
- Original Message -
From:
Stacey
Verner
To: Multiple recipients of list delphi
Sent: Friday, October 19, 2001 10:39
AM
Subject: [DUG]: Debugging Troubles
I have an
application which is
Call
TForm.Release(). This posts a message to the form's queue that will cause it to
destroy itself.
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bob
OsbornSent: Friday, 19 October 2001 11:23 amTo: Multiple
recipients of list delphiSubjec
In the
FormClose event I remove the form from our internal list of forms, and then
call Release.
Stacey
-Original Message-From: Paul Grimstrup
[mailto:[EMAIL PROTECTED]]Sent: Friday, 19 October 2001 11:30
a.m.To: Multiple recipients of list delphiSubject: RE:
[DUG]: Debug
I am
calling Release in the OnClose.
This
was all working well in D4, but we have made major changes during the upgrade to
D6.
Stacey
-Original Message-From: Bob Osborn
[mailto:[EMAIL PROTECTED]]Sent: Friday, 19 October 2001 11:23
a.m.To: Multiple recipients of list delph
Stacey
Is this necesary? In the onclose I'd just remove the form from your internal
list, I think you may be initiating another message to the form
HTH
Nevne
- Original Message -
From: "Stacey Verner" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent
This is an MDI app, and when a form closes in an MDI environment it simply
minimizes to the bottom of the main form, and therefore doesn't release its
memory, and looks damned ugly!
Stacey
> -Original Message-
> From: Neven MacEwan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, 19 October 20
I believe the approach is sound, and has worked well for 4 odd years. The
problem will most likely be very simple, its just impossible to find out
where its going wrong because the call stack doesn't show me much.
Stacey
> -Original Message-
> From: Neven MacEwan [mailto:[EMAIL PROTECTED
> This is an MDI app, and when a form closes in an MDI environment it simply
> minimizes to the bottom of the main form, and therefore doesn't
> release its
> memory, and looks damned ugly!
>
In the OnClose handler of the MDI Child form:
procedure TForm1.FormClose(Sender: TObject; var Action: TC
Well, yeah - but how compliant are the other parsers? the MS one and
especially the IBM one, is very compliant.
N
- Original Message -
From: "Neven MacEwan" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent: Friday, October 19, 2001 9:50 AM
Subject: Re:
Stacey asked about a nasty Windows event exception:
> How do I go about debugging a problem like this?
The best approach that I can think of, baring the Zen method of just fixing
it 8-), is to do some serious event logging in your code.
This kind of event being sent to a destroyed handle is ver
Nic Wise asked:
> Well, yeah - but how compliant are the other parsers? the MS one and
> especially the IBM one, is very compliant.
Well, the OpenXML native Delphi parser is so compliant that the author has
found several bugs in the actual XML standards that he had had to get
resolved by the com
Except of OS Max :-)
- Original Message -
From: "Max Nilson" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent: Friday, October 19, 2001 1:28 PM
Subject: RE: [DUG]: Setting Attributes in XML
> Nic Wise asked:
>
> > Well, yeah - but how compliant are t
Fair enough - and as someone asked yesterday, you could make it plug into
the Borland framework, if you really wanted to
N
- Original Message -
From: "Max Nilson" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent: Friday, October 19, 2001 1:28 PM
Su
Nic
Have I been reduced to 'someone' or are you having a bad day
Neven
- Original Message -
From: "Nic Wise" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent: Friday, October 19, 2001 1:50 PM
Subject: Re: [DUG]: Setting Attributes in XML
> Fair eno
You asked? I didn't recall seeing you there :( :( :(
Sorry, the last 3 days have been a bit of a haze - rather tired after doing
2 weeks of back-to-back training, plus having my laptop nicked, then doing
the road show etc etc. sorry :( Hence why I'm taking today off :)
Nic.
- Original
Ah, so that was Neven!
Was it just me or did anyone else wish Borland had made the names on the
nametags a little larger so they could be read from a discreet distance? (I
didn't want to be caught peering too closely! ;-)
David.
- Original Message -
From: "Neven MacEwan" <[EMAIL PROTECT
:) thanks for the comment - I'll forward it to Ashleigh and Alice - see if
we can fix it for next time :)
Of course, people with very long names may have to "miss out" on that
:)
Nic.
- Original Message -
From: "David Brennan" <[EMAIL PROTECTED]>
To: "Multiple recipients of list de
Sorry Nic
I'm confusing you, I posted a message the other day re this,
No I did not indulge in your training, (currently bum down moving
all my 'stuff' to D6)
N
- Original Message -
From: "Nic Wise" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent: F
I had an app exibiting random crashes. After running memory Sleuth I
discovered that my TForm.Free and / Or TForm.Release statements were failing
to trigger (app was a similar structure to yours). In the end I Set Action
:= caFree and called close instead for free, my forms then correctly
releas
After beginning to
head down Max Nilsons suggested path, I decided to try doing Action := caFree
instead for Release, and it works fine.
I am unsure and
wonder why? (but happy anyway!)
Whats the difference
between Release and Action := caFree are different?
I thought they would
have end
The Close method calls
the OnClose event. If it returns caFree then the Close method calls Release.
Release posts a CM_RELEASE message
to the form. If you are calling
Release in the OnClose event handler, then Release gets called twice, which
means the second message tries to get processed
Steve
I have a handle on this problem now.
Are you still interested?
It's kind of involved - if you are i can post to the
offtopic list or we can take it to email.
I've seen this thing before and have been ignoring it
up until now so thanks for the push.
-ns
http://www.roserox.co.th
- O
30 matches
Mail list logo
