LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Using set cursor.vi in an executable

I am running the VI and the executable on the same PC.
S G
Certified LabVIEW Architect, Certified TestStand Architect, Certified Professional Instructor
0 Kudos
Message 11 of 19
(1,896 Views)
While I can't offer a solution, I can confirm the problem you're having. I'm on 8.2 and I can set any cursor in the VI, but not in the executable. I'm not sure why this is, maybe an applications engineer can shed some light on the problem.
Message 12 of 19
(1,863 Views)
Some of the cursors, such as the paintbrush mentioned in an earlier post, are only relevant in edit mode and you cannot edit a built application. I do not see anything in the documentation, but this may be what is happening. Are the inaccessible cursors ones which are only used in edit mode?

Lynn
0 Kudos
Message 13 of 19
(1,857 Views)
You may be right.  Somebody from NI needs to confirm this.  However, if that is the case, I should not be able to set the paintbrush cursor in a VI that is running, because it is no longer in edit mode, but in run mode. 
 
Also, I am not able to use custom cursors from a .cur file in a built application even though I successfully use them in a vi.
 
 
S G
Certified LabVIEW Architect, Certified TestStand Architect, Certified Professional Instructor
0 Kudos
Message 14 of 19
(1,850 Views)
This is actually a known issue that some of the cursors will not show up in an executable. R&D is aware of the problem and they are currently working on a solution. One workaround that I am aware of is referencing the cursor in a file. That is Create Cursor From File.vi plus the Set Cursor.vi. However, you will need a cursor file that has the cursor in it. I hope this helps!
Nick R
NI
Message 15 of 19
(1,818 Views)

Hi Nick,

Do you have a CAR# that goes with this issue?

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 16 of 19
(1,745 Views)
The CAR ID is 3MJMKBSG.
Nick R
NI
Message 17 of 19
(1,737 Views)
Thanks all.  I am using a custom cursor file now, and that seems to be a workaround.  Be sure to include the cursor file (.cur) in your application if you plan to use this method.
S G
Certified LabVIEW Architect, Certified TestStand Architect, Certified Professional Instructor
Message 18 of 19
(1,724 Views)
This was reported to R&D (# 3MJMKBSG) for further investigation.
Nick R
NI
0 Kudos
Message 19 of 19
(1,640 Views)