vugie

One serious limitation is that the wire cannot cross with itself - so cycloides chenged to chain of arcs. BTW, I found strange issue with property Joints[] of the Wire class. It describes actual wire bending and is marked as read-only in docs. There are some flags and few of them are marked "do not modify" (?!). I would like to be able to modify some read-only properties... But for property node option "Change to write" is not greyed-out, however modyfing writing to this property results with "Property doesn't exist". Quite strange, isn't it? LV82

That was only the start... Attached what it was created with. No description, no comments, no even icons - I warned you. wired-wires.zip

I also had that idea. It's quite fun - I'm still playing with it and all that brought me to idea for coding chellenge: "The most wired thing you can do with wires"

Just to prove that it is technically possible: Yes, programmaticly: Sorry for not closing references, etc.

That definitely should be the part of RCFs competitor - Wrong-Klik Framework. With such plugins as "finish this project", "Get the idea", "Solve this problem", "Earn money for me" and less spectacular but still effective "Wire diagonally", "Zoom out", "Measure wires cross-talking" or "Ask on LAVA why this is not working". Some of us will also welcome "Generate post for alpha thread".

Hard to say... Most of he problems on LV is solved or is on the straight way. I'm stucked in Flash/ActionScript mess now. The tool I used has its limits and is not developing in direction I expected. There are hundreds of other tools and libraries but it is hard to find something which satisfy my requirements. And for me - still hardly knowing the subject - it is even hard to judge whether my requirements are satisfied... September should be realistic.

If speaking as generally as "creating new file format" I would agree. But how specificaly how should this format look like to be usable? It should more or less strictly reflect internal LabVIEW class hierarchy and this may already be treated as reverse engineering - not the VI format, but LabVIEW itself. And creating such format trying not to mimic class hierarchy? Nonsense - it would look like esoteric programming language (BTW, which of them do you like most? ) In my opinion, even thinking about such a format makes no sense as so many aspects of VI is not exposed (even as private classes): from less important like decoration content, to extremly important like recently discussed event structure management. All we can afford is human readable (limited) macro programming language... but would it be better than just scripting?

Well... I'm just working on sth like this. Features planned for next release: Exporting given VI and (possibly selectable) subVIs up to certain nesting level to navigable SWF file. Only browser with Flash plugin is required to view the file. Switchable multiframe structures (Case, Event, etc.) for any nesting level Only pictures are exported, not the code Docs and connector pane for all exported VIs Descriptions displayed as tips for all objects on BD and FP of selected classes (functions, subVIs, vi.lib VIs, terminals, etc.) Simple GUI for navigatinon within SWF file: Selectable list of VIs, BD/FP switching, zooming, panning, scrolling

That one who knows real number of disadvantages...

Thanks a lot If anyone here knows (or wants to know) ActionScript I would appreciate any help.

Because picture control has such On the front panel you have to switch to set color tool, right-clik on picture control and select transparent color (upper-right corner, marked with T) And the angle for rotation should be in radians proba transp.vi

I know, I'm flooding the forum today... I would like to share with you method for creating icons I invented recently. Up to now I used great Mark Balla's icon editor (and I still use it sometimes). But whole the time it was hard to remember which bakcgroud color and which abberation mean what, simply to fit on the icon all the information I need using only limited amount of text and few colors. Besides this I simply like graphics on icons. But preparing graphical icons using LV editor is time consuming as well as using external editor and copy-pasting (which often leeds to some confusion as LV uses its own 200+ color palette). What's more LV don't update smaller bit depth versions of icons - even if one don't care about them (who cares nowdays?) they should look at least different then default ones. To prepare graphical icons efficiently you have to have prepared common backrounds for projects or separate parts of code, glyphs for classes, glyphs for common actions as get, set, read, write, etc., glyphs for most important datatypes, some arrows or other symbols. If you have such a library (of course it is being created as project grows, parts may be imported from icon themes as Tango or Nuvola). I started this approach for the project I call temporaily LVODE. It is set of wrappers with some my code for Open Dynamics Engine (ODE) (BTW, I plan to relase it to public and although it is already pretty usable for me and even documented, I need some motivation to make it usable for others). I decided to use Inkscape - vector graphics editor. My icon development environment looked like this: I was arranging icon by few moves of mouse (when not creating additional glyph), selecting it and exporing as 32x32 png file with always the same name. For importing to LV I wrote a VI I put to Tools menu which retrieved current VI reference and used "VI icon.Set from file" method. Pretty efficient but there were 2 major problems: color conversion from 24-bit image to indexed color icon sometimes led to ugly colors and interpolation of vector-raster conversion often caused limited readability of an icon. Then I moved to GIMP. It is raster image editor, uses layers and has native indexed color support. I exported LV icon palette to ACT file, imported it in GIMP, so I was able to draw using target colors. The icon development environment looks now like this: Glyphs and backrounds are located in separate channels - I simply turn on/off their visibility, there is also a possibility for editable text layers. It was little bit tricky to find font and options to be able to write readable text with small font size. Now the best part: GIMP has so called Script-Fu - macro language to perform automated tasks. It also has Script-Fu server making it able to receive commands via TCP. So when the icon is made I do not have to export anything - just switch back to LabVIEW select a command from Tools menu and voila! Here is VI which do the trick: Maybe GIMP is not so efficient and elastic for creating icons as Inkscape was (belive me - I was able to prepare an icon with some glyphs and text in 15 s), but this is the price for guarantee of readability. Now one icon takes me 0.5-1 min and it is always worth that time. And I hope that some day my experiences and ideas will grow into new GRAPHICAL icon editor as fast and convenient as Inkscape and generating as nice effects as GIMP. ------ I was writing this post quite a long time uploading images successively as I was writing and after some time I wasn't able to upload anything more (Upload failed)... I had to start topic again. Is time to write the post limited?

Is it possible to give Code Repository entries back to their authors? Not even talking about updates, they could at least upload previous screenshots.

Correction: "Picture to Pixmap" generates 24-bit image data (without a mask), so no transparency is preserved here in any form.

I found out that links in LAVA 1.0 content which pointed to another threads in LAVA now point to completly other threads, totally wthout sense. This is because links were coded as topics numbers and that numbers are different for new forum. Maybe it would be possible to automatically parse the old content in order to generate a list of posts with links to other threads and send this posts (as links to new forum) to their authors. Then the authors would correct the links (if they remember what they meant).

It's not possible with ActiveX. You may use command line parameters as described i.e. here. Alternatively you may simulate user interaction using shell's ActiveX as described here.

I attempted onece to use GOCR- open source command line tool. I don't remember exactly how it worked because project I used it for died at the beginning.

You might be also interested in this solution.

You loose transperency in both 1st and 4th stage. In 1st because "Picture to Pixmap" stores transparency only in 4th byte of 32-bit image data, not in the mask. You have to manually convert this data to mask and perform your operations on the mask as well. But I've noticed that the transparency data generated by "Picture to Pixmap" in not compatibile to similar data generated by "Load PNG"... Bug? I have to do more testing on this. If you know something about the image you may generate mask yourself from color image data (i.e. using "Create Mask"). I would reccomend you using my BitMan library which helps with such situations and perform all operations on transparency automaticly.

This glow is the main reason I wanted this banner to be changed

Sorry for doubleposting, but where is the edit button? [edit]THIS post has edit button, previous one had not (even when it was the last one) [/edit] I'm not too convienced that it looks too much like BD and why it should not, but ok - what about this? (background color is same as current one) Yeah, the Web 2.0 style... forgive me.

I don't know what "View unread content" is actually showing. I everyday find a topic simply browsing forums which I didn't read and which was not showed in VUC. And the same with new post. Is VUC limited to some boards or sth like that? I'm not able to find a rule. Same situation for code repository files - just compare box with latest files showed on portal page to code repository tab in VUC. I would like to simply see the list of all latest posts with user, date and board. I know better what I've read and what not.

Of course it is little bit late, and generally you shouldn't take me too seriously, but now I would change this slogan to "Don't let live them with such a documentation!"

I'm going upload the code after making it really usable and with at least trace of documentation. Now even I has sometimes a problem to remember where I put top level VI... Because it's a member of a class and it is not obvious which one it should be. I already tried the flipped version of logo but it doesn't look too good. I don't know why... Creating universal text-based format for VI was already discussed few times as I remember. BTW it is a good subject for LAVA cooperative project, LAVA flagship or how too call it... I can think of many advantages of such a format and related utilities. With VIpreVIEW I capture too less information for such an approach - just images of subsequent frames of multiframe structures and some text and position info from other objects for displaying tips.

No... LAVA has always looked in opposite direction... Noise is here second order thing. When you change V to equivalent and more elegant compound arithmetic node it won't be too readable