01-02-2009 11:25 AM
Solved! Go to Solution.
01-02-2009 11:44 AM
This is my first attempt, which seems to be failing miserably (attached).
I found a bunch of HTML controls, but it looks like I would have to make a property node for each one.
IE, one for body, paragraph, font, color .... etc.
It would be much easier to just type the whole thing out as a string control.
Am I at least going in the right direction with my VI?
01-02-2009 12:15 PM
Hi there
Save the HTML in a tmp file and use the "Web Browser" control from the ".NET & ActiveX" palette for display. See attachment.
01-02-2009 02:03 PM - edited 01-02-2009 02:07 PM
The poster has LabVIEW 7 (can tell by opening his VI) so they cannot open a LabVIEW 8.5 VI.
To Cory: You are not properly using the event structure. Since there is no timeout on the event structure the loop will not stop when you press the Stop button since the event structure does not fire, and the loop is waiting for the event structure. You should have an event case to handle the Stop button and pass out its value to the loop's termination terminal. There is no need for the Wait function. When the event structure has no timeout value wired then it doesn't do anything (thereby consuming no CPU cycles) until an event occurs.
Note: The above is not the reason why your VI doesn't work. Your specific problem is that you are just not using the DOM correctly. The alternate solution proposed by Cory is simple and straightforward, though it requires the creation of a file on disk, albeit one that can be safely deleted.
01-02-2009 02:20 PM
There you are (not sure about the 7.0 Version). See attachments...
01-02-2009 04:40 PM
01-02-2009 04:44 PM
10-06-2009 06:26 AM
Hi
When I run the VI it say's that something has change and the VI need to be saved.
Why is that?
Regards Bjarne
10-06-2009 08:56 AM
10-07-2009 01:05 AM
Hi
I was HTML_71.vi I was running under LV8.2.1.
I think you are right about the version of the activeX comp., but how do you manage it when you are distrubuating the vi to other machines(PCs). If the user upgrade the webBrowser on that maschine, you got the problem.
There is another problem to.
If you make the VI and do NOT run before you save and close it. Then when you open the VI again it look normal(no asterix that indicate that the VI has change). If you the run it you got an asterix and when you close the VI you will be promt to save the vi.
regards Bjarne