Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

DHTML refresh problem in HTA

19 views
Skip to first unread message

Lionel Fourquaux

unread,
Nov 16, 2002, 4:27:35 PM11/16/02
to
Hello,

I'm trying to write an HTA interface to modify some registry setting (using WMI).
My "application" creates a table of parameters, with several buttons to add/delete
rows, and has a strange disfunctionment: if I add a row, then delete it, then change
nodes in another row, the new nodes aren't displayed at all. If I move the mouse
over one of the modified field, it appears if I changed it into a text node, and it
appears and I get an error message:

Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:\WINDOWS\System32\mshta.exe
R6025
- pure virtual function call

(and mshta exits) if I changed it into a test input field.

If, instead of moving the mouse, I add another row, the modified fields appear
without error.

This behaviour is so strange that I doubt it can be caused by my code, and I have
been unable to reproduce it in a small example. (The full code is a 13Ko file,
and I won't post it here).

I'm using mainly appendChild, replaceChild, setAttribute, getAttribute, attachEvent,
detachEvent, childNodes, firstChild, and the rows and cells enumerations of the
table object model. The scripting language is javascript (even for WMI, although
it's more complicated to call WMI methods).

Is there some kind of known bug in this context, or some well-known programming
error, that could explain these refresh problems and the runtime error I see?

Thanks in advance for your help.

Lionel Fourquaux


Lionel Fourquaux

unread,
Nov 16, 2002, 4:34:13 PM11/16/02
to
I forgot to add this: it's on a WinXP Pro system, IE6, with all security patches applied.

Lionel Fourquaux

Lionel Fourquaux

unread,
Nov 17, 2002, 4:39:58 PM11/17/02
to
After several hours spent searching in the documentation, I found what the problem
was: I was mixing DOM calls with table object model enumerations. Using only
DOM fixed it.
Thanks to all who thougth about my problem.
Lionel Fourquaux

0 new messages