DanielChile

Unless someone comes up with a fancy way to do this... I would just Alt-PrintScreen the LV exe, put it into the picture editor of your choice (MSPaint is easy to use) and cut-n-paste your graph to the Word doc. I've done this a few times in the past and it's relatively painless.

Cat

Well, in that case you really don't need to use the picture editor, you can paste directly in MS Word.

Drag and drop would be nice.

Thank you.

Daniel R.

Hello, everybody.

¿Is it possible to drag an XY Graph from the front panel of a LV executable and drop it in a Microsoft Word document?

That would be a great feature in our analysis software.

Daniel R.

PD: I'm using LV 8.5.1.

If you want to do this programmaticly, then take a look at the NI Web Service Server in the code repository. There is a VI in there that uses .NET calls to do this for you. Feel free to use that in your project. Only works with Windows, however...

Thanks, John.

Do you know if I can find this for LV 8.5.1 anywhere?

Regards,

Daniel R.

If you like trouble you can take a picture with your cell phone and email it for few $.

I couldn'd think of that by myself.

Another thing that I could do is take a picture of the screen with my old film camera, develop the film, put it on my scanner and voila!

(just kidding)

Daniel R.

In LV 7.1 I have an invoke node for the VI called 'Get Panel Image'.

Here's a code fragment, that gets the frontpanel of a VI. You can save this to a file (PNG, JPG, BMP)

Thanks, Felix and Jens.

Actually, I need to get a full screen image, not only a front panel.

I was thinking of .NET or Activex, but still haven't found the right piece of code.

Regards,

Daniel R.

Sorry, everyone, I forgot to mention:

1. Get a screenshot programmatically

2. Working with LV 8.5.1.

Thanks a lot,

Daniel R.

Hello, everyone.

What is the easiest way to get a screenshot? Make your bets.

Thanks,

Daniel R.

Hello, everyone. I need help from the UI masters.

Please see the attached VI (LV 8.5.1). You may notice an ugly "xxxxxxE-15" on the Y scale of the graph where it should be a simple zero. Note that this scale has scaling factors.

I suppose this is a bug and we wanted to workaround it. We figured out that we could read all markers text and then just write a "0" to the ugly one, but we still can't get the right method.

Any suggestions?

Daniel R.

QUOTE (Wim @ Nov 21 2008, 09:08 AM)

it would be nice to add a standard windows network pc in the targets for projects.

this way it would be easy to develop and maintain software on a local pc and then deploy it on a network pc like you can do for cRio or other NI devices.

It seems difficult that Microsoft gives you permission on that.

Daniel R.

QUOTE (rolfk @ Oct 27 2008, 05:31 PM)

Actually I haven't. Have been in communication about it at some time with them and you can request an evaluation version, so I think it should be fair.

Rolf Kalbermatter

All right. Thank you so much for your answers, everyone.

As always, LAVA has been very helpful.

¡Long live to LAVA!

Daniel R.

CLD

Thank you for your answer, Rolf. Very complete references.

SEA toolkit seems good to me. Have you tried that?

Regards,

Daniel R.

CLD

Thanks for your answers.

So it seems that any real (professional) solution to this means building your own "translation engine". Tricky.

Thank you,

Daniel R.

CLD

Hi everyone,

I was wandering: ¿How do YOU manage different UI languages in your LabVIEW-built software?

For example, we have exported VI strings in the original language of our software (spanish), then edited the VIs for translation to english and re-exported the strings, so now we have different sets of string files for different languages.

At edit time we can manually import strings for every user interfase VI and then compile for different languages, but I was asking myself if there could be a better way. For example, I was thinking about importing the strings programmatically at run-time, but this is not possible, because "VI Strings.Import" method is not "Settable when the VI is running".

Any ideas?

Daniel

Perfect. Thank you for your fast answer.

See you,

Daniel R.

QUOTE(Aristos Queue @ Jan 22 2008, 02:41 PM)

Make the functional global itself be a template VI. Then drop the *template* on the block diagram of your other template. The subVI node will be decorated with a large black capital T, indicating that when the top level template is instantiated, this subVI will also be independently instantiated. Now you'll have a separate functional global instance for each of your top level template instances.

Hi all.

In the development of my application, I include a vi template for certain visualization window, so I can open unlimited number of instances of that window.

Now, I would like to use a Functional Global Variable inside this window, but not share it through all of them.

Now, from my tests, I found no way (execution options) to do this.

Any suggestions?

Daniel R

Hi everyone. I'm considering to buy a tablet PC (HP tx1230) instead of a regular notebook.

Has anyone tried to program LabVIEW using the tablet stylus instead of a mouse? How was it?

Thank you

DR

QUOTE(yen @ Aug 28 2007, 02:50 PM)

As far as I know, there isn't (at least there wasn't in 7.1. It may have been added as a private property in 8.x).

You can do something like http://forums.ni.com/ni/board/message?board.id=170&message.id=249633' target="_blank">this instead.

Thanks for the answer. However, I was thinking about a boolean control, so there is no choice for "invalid" values.

DR

Hi all. I was wondering if it exists a "wired?" property (or something like that), so you can programmatically know from a subVI if certain control is wired or not (on the top VI diagram).

Am I clear?

Thank you.

Daniel Ramírez

CADETECH S.A.

Hi everyone, thank you for your comments. They helped me think about what could be the best "workaround" (for me) on my wish. It's all about how everyone feels more comfortable.

At least for me, commenting out code must be as fast as possible. For example when writing a short comment on the diagram, is not the same to put a label (three tab hits to select text tool, one click to position on diagram, write and enter) that to put a string constant (one right click to make functions palette appear, move mouse over or click "string", click on string constant, click to position on diagram, write and enter) (4 steps versus 6 steps, 50% less). I might be exaggerating but for me these things make the difference between a well documented diagram versus a bad one.

Between suggestions you made I liked the most the description of a constant. However, I don't use the context help window very often, because I find it takes too much valuable screen space. So, instead of the constant description I suggest writing on its "tip strip". When using the "hand" tool and hovering over the constant will make the comments appear, almost as I wished on my first post. Is not as fast as inserting a label, but I find it good enough.

Thank you! :thumbup:

Daniel R.

Although I develop LabVIEW applications alone (not on a group) I always try to comment out the code as much as possible, including ideas for future development or improvements (refactoring).

Constanly I find myself reviewing code after several months and, as you may know, I appreciate a lot the notes I leaved to myself. (Have you seen "memento"?).

The only drawback is that (at least up to LV7.1) you end your diagram with a lot of "dead" areas occupied by comments, which leads to (even) greater diagrams where you have to scroll a lot (more).

I would like to see comments as little icons that when the mouse hovers over them show the complete text. Or maybe instead of an icon could be the first words of the comment plus "..." dots, I don't know.

What do you think?

Daniel R.