Changing mouse cursor using Set Cursor.vi doesn't work when built as executable

[Todd_SD]

I have an event handler that sets the mouse cursor to a paint brush on 'mouse enter' on a picture control and to an arrow on 'mouse leave'. This works great when I run the VI, but when built as an executable, the paint brush will never show up. In the attached executable you can see an example of this and also change the cursors on the fly. Most of the other cursors will work in the executable, but some don't. Anybody know why?

[chilly_charly]

I have checked this stupid behaviour on my machines (W2K and MacOS). This seems to be a bug, and I don't see any workaround. Sorry !

[Todd_SD]

---

@chilly charly wrote:
I have checked this stupid behaviour on my machines (W2K and MacOS). This seems to be a bug, and I don't see any workaround. Sorry !

---

Is there some bug report that I should file for this? What do we do when we find something wrong?

[chilly_charly]

I already reported this as a bug. The easiest way to do that is to post a link here

Message Edited by chilly charly on 06-17-2005 09:12 AM

[zou]

This probably is not a bug, but removed intentionally because NI think you don't need it. It's for edit mode, not run mode.

A work around: save that cursor to a cursor file, load it dynamically in runtime.

George Zou
http://gtoolbox.yeah.net

[chilly_charly]

---

@zou wrote:
This probably is not a bug, but removed intentionally because NI think you don't need it. It's for edit mode, not run mode.

A work around: save that cursor to a cursor file, load it dynamically in runtime.

George Zou
http://gtoolbox.yeah.net

---

Don't see what you mean. Why should that be a problem only with executables ? Could you provide us with an example ?

[Philip_Courtois]

Hi Todd,

Yes, I agree that this seems like a bug. Therefore I have officially reported the behavior to the R&D department under the title "Executable doesn't support all cursors when using the Cursor VIs".

I appreciate that you made it so easy to reproduce the issue. Your example was great!

Thanks!

[Leonid Kuzmin]

I have a base-version of LabVIEW 7.1 with IMAQ Vision, becouse of that I havn't the VIs for manage cursor, but I try to make the same actions by Call Library Function and WinAPI parameters. And I have the same problem:

In edit mode I have no problem, bu in EXE-file, when I draw some line (ROI) on the picture (IMAQ Image Display) the cursor changes from "finger" to "move" (4ways-arrows). Move-cursor is keep staying while the user not moves out the mouse from the image area.

I understand, that this bug has place to be, but does anybody find the way to solve this problem in EXE-file?

[DJ_L.]

Hey Leonid Kuzmin,

When you draw an ROI on an Image Display, it is expected that the cursor change to the cursor that is set for the ROI tool. Now after you draw that ROI, if you hover your cursor over the ROI, then the "move" (4ways-arrows) will appear, and that too is expected behavior. This is because the Image Display thinks that you are wanting to move the ROI somewhere else on the image. This is expected behavior for when you are in both edit mode and EXE mode. If you move the cursor off of the ROI then it should change back to the ROI tool, and if you move outside of the Image Display, then it will change back to whatever you have it set up for. This is not an issue, but it is more of expected behavior of the Image Display properties.

I hope this answers your question. Let me know if you were talking about some other behavior. Thanks.

Regards,

DJ L.

[Leonid Kuzmin]

I see, that you're not testing the same VI in edit-mode and in EXE-file.

Try to do this and you'll see the difference between cursor after you drow some ROI and replace cursor from ROI (but not outside the Image-area).

Cursor in edit-mode will be changed to little cross, but in EXE-file will be the arrows (depends on ROI-tool you're using).

That was my problem, that I solved by VIs witch is included in LV7.1Pro-version.

P.S.: In my EXE-file all CursorVIs are workin' well, I had no problem.