Pulsonix User Forum

Technical advice from Pulsonix engineers and the wider community.

Username:
 Password:
Save Password
Forgot your Password?

 All Forums
 Help with using Pulsonix
 Scripting
 Node.Name inaccessible
Author Previous Topic Topic Next Topic  

MK_CZSMT

Germany
4 Posts
Posted - 14 Mar 2022 :  16:56:30  Show Profile
I'm trying to find out all components attached to each net in the design. However, it seems to work to get the list of nodes but the node names cannot be accessed. Even my sanity check 

if (Node.Name Is Nothing)  then


fails with error Scode:800a01a8
complaining about a missing object or so. MWE appended.

Download Attachment: NodeNameMWE1.txt
1.63 KB

lewism@pulsonix.com

United Kingdom
62 Posts
Posted - 14 Mar 2022 :  17:37:54  Show Profile
Hi,

Looks like the issue is with the line;

if (Node.Name Is Nothing) then



This visual basic function I think does the job.

if (IsNull(Node.Name)) then



using 'Node.Name Is Null' or 'Node.Name Is Empty' doesn't seem to work.

I hope this helps.

Lewis
Go to Top of Page

MK_CZSMT

Germany
4 Posts
Posted - 15 Mar 2022 :  16:54:28  Show Profile
Amazing,

it works. Now could someone explain to me why I have to use isNull for Node.Name and isNothing for Net.Class? I don't understand, why the tests for existence have to be different? Are they different data types?
Go to Top of Page

lewism@pulsonix.com

United Kingdom
62 Posts
Posted - 16 Mar 2022 :  10:16:07  Show Profile
Hi,

I'm not sure to be honest, this isn't really an issue with Pulsonix software itself, so I cant be much more help I'm afraid.

Lewis
Go to Top of Page
  Previous Topic Topic Next Topic  
Jump To: