image size?

[Hatef.fouladi]

Blokk

Thank you for your post  I am so sorry for make misunderstanding by typing work in capital latters indeed my keyboard sometimes got problem in typing and I never intend to make sense of  shouting just my caps lock was in on mode  and I do not care about it in fast typing
forgive me for this mistake and I am sorry about that

also I try to give solution with vision because one my area of interest in labview is vision and image processing so i work with vi of this toolkit a lot
also unfortunately I could not use Code Capture Tool because I  use an other tool that make me some serious problem in my coding process  if I use Code Capture Tool

thank you to clear out it to me and let me know  about it

[tst]

---

@Hatef wrote:
I could not use Code Capture Tool because I  use an other tool that make me some serious problem in my coding process  if I use Code Capture Tool

---

This is off topic, but what is the problem there? We won't necessarily change the CCT, but it's useful to know if there are problems.

[mattstiles]

Thanks all.  Setting the image size programmatically solved my problem.  What I was seeing made me afraid that when I drew on the image with pixel coordinates I might be off by some pixels, but that doesn't seem to be the case for the most part.  I think some trial and error is required if I want to be sure to work with exact pixel coordinates.

[Hatef.fouladi]

Sorry to answer here I try to send you PM but it seem it is not possible 
my problem was that then I use this toolkit 
I could not use drag and drop between vis 
also I could not use copy the code between vi 

[tst]

---

@Hatef wrote:

my problem was that then I use this toolkit 
I could not use drag and drop between vis 
also I could not use copy the code between vi 

---

I don't see any reason why that would happen. The CCT is just a bunch of files that sit on disk. When you launch it, it's a modal window, so you can't do anything else, and it does write to the clipboard when you capture, but other than that I don't see any reason why it should prevent those things.

The only thing I can think of is that there is some kind of problem with your clipboard and the code that the CCT uses to write to the clipboard triggers that problem or that some call doesn't work under a specific OS (copying the path to the clipboard is a built-in method, but copying the image itself calls some Win32 API functions).

If you want to avoid hijacking the thread and want to try to resolve it, you could try posting the details to the support thread here - https://lavag.org/topic/10309-lvtn-code-capture-tool/