Ton Plomp
-
Posts
1,991 -
Joined
-
Last visited
-
Days Won
38
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by Ton Plomp
-
-
-
Hi Jim/Tomi,
the following code works:
I had to extend {VI match XControlName}
Ton
-
-
QUOTE(mross @ Feb 17 2007, 03:30 PM)
In that case I'd suggest the https://addons.mozilla.org/firefox/424/' target="_blank">Wizz RSS reader
It adds a pane to your browser with a tree of all sub-scribed RSS feeds.
Some interesting, are listed in the 'blogs section of LAVA.
Another cool feature is the listing of Info-LabVIEW in Gmail, i've added a info-labview label, and let Wizz RSS list that label as a seperate RSS-feed!
On the NI-forums you can have RSS feeds for every board (LabVIEW/DIADem/Breakpoint :thumbup: ) and for specific users/keywords
Ton
-
QUOTE(Aristos Queue @ Feb 16 2007, 04:22 PM)
File the bug report if you want, but it'll get closed "Not A Bug." :-)Not reported because I realize it is how it is meant to be
It is more a convenience issue, we have some GPS lvlib's, where the main datatype is a typedef with 10 or so elements including 4 enum's.
So for a program where I want to build data for the lvlib or display data from the lvlib I set my data-cluster to public. The reason for the public datatype is that it is just a subset of all data we've got (that is about 40 elements, mainly debug). But in order to use the public datatype, all it's enums have to be public also, not really an issue but an inconvience, the structure of the public part of the lvlib grows unnesecarily in size...
So I've decided to just declare all my controls private, making it look more complicated than it is...
Ton
Sorry it turned kinda into a rant post, not meant to be
-
QUOTE(berndr @ Feb 16 2007, 09:45 AM)
Isn't it possible to run LabVIEW with relative paths? Do you have an idea how the problem can be solved? Or is the only solution to use on every development plattform the same paths for the application and the LabVIEW distribution?LabVIEW has a limited set of relative paths:
vi.lib, user.lib and inst.lib
If you only refer to files inside these paths (or relative to the VI itself) there won't be any problem, at least we haven't seen it with SCC, just make sure you build from one root!
Ton
-
QUOTE(crelf @ Feb 15 2007, 10:05 PM)
I thought you had your own http://forums.ni.com/attachments/ni/BreakPoint/1408/1/NI%20Gift.png' target="_blank">star?
And why do we have to bring our own hardware? I might have a 4 slot 3M CRIO chassis, but that's all.... :laugh:
Ton
EDIT:
The link to monster doesn't work?
-
Consider the following, you have a library that has private controls. For use inside other VI's you construct a typedef .ctl that contains some off these controls and make the typedef .ctl public.
Now if you use this typedef inside another VI/Ctl the VI/CTL will be broken since it refers directly to the private members :thumbdown: . I was hoping that the public .ctl refered to the private members allowing a good use to these items....
Does anyone have an idea why? and how to bypass this.
The error:
This VI cannot access the referenced item because of library access scope. Private library items can only be accessed from inside the same library or libraries contained in that library. Protected library items can only be created inside LabVIEW classes and can only be accessed from inside the same LabVIEW class or LabVIEW classes inheriting from that class.
Ton
-
QUOTE(Tomi Maila @ Feb 14 2007, 07:52 PM)
One thing that could work is to force a control on XNode generated front panel visible somehow. By default both the XNode generated code and the front panel elements are all hidden.Tomi
Well now my sick twisted mind kicks in.....
What we need is an Xnodes\XControls twin....
It will be kind of hard, but let's handle the xnode do the polymorphism, and convert the data into the generic datatype you'd like to use and port that into the XControl, maybe together with a datatype changed? signalling boolean.
One other thought is just a normal polymorphic VI '1' (one) pixel wide stitched to the XControl, and have a merge VI contain both, maybe that is better, but true XControl polymorphism would be wonderfull!!!
Ton
-
This is not about the display of the XControl, but about the terminal and datatype of the XControl, and I think Aitor knows his way with Xnodes... Maybe this can be gold pot under the rainbow?
Ton
-
QUOTE(Aitor Solar @ Feb 14 2007, 01:23 PM)
Let's say you make a XControl of a graph. Graphs are polymorphic (for example, a Waveform Graph can accept 1D or 2D-array data), but the XControl doesn't. Any workaround?Saludos,
Aitor
Variant?
I don't think there is an easy work around since the datatype is defined with the data ability, which is a typedef, and the beauty of typedefs is that they restrict the data type.
Moreover you should be able to handle all kinds off data inside your facade VI, quite hard I can imagine!
Ton
-
QUOTE(PJM_labview @ Feb 13 2007, 10:40 PM)
Note: The TDMS File viewer is pretty cool too.Although I should not be too surprised of these bugs since I broke the golden rule of never using new LV features until they have matured...
Note: One of the thing missing from the API is a delete TDMS file that would delete both the tdms file and its index.
Just one bug in the TDMS File viewer, it doen't respond on panel close..., So if you have it in your program, you load it automatically and the user closes the panel (not using quit) you have a running sub-vi you can't exit.... It is just a little extra programming but aaahhhhh
Ton
-
QUOTE(Omar Mussa @ Feb 10 2007, 02:14 AM)
Will be posting a few 'feature requests' too through NIs forum...I have added one as well, because of this 'challenge'. I noticed you looked for the wrong pane when resizing. Currently renaming a pane is quite cumbersom (right click on divider, show pane label, rename, hide pane label), so I added a feature request to show a naming pop-up on adding a divider.
Ton
-
No idea (interesting behaviour though), but I just wanted to say that I see this too on 7.1.
Same in 8.2 (1800 vs. 17 ms)
Ton
-
I also have been living with this problem, every time I want to resize a column I go into the options and select none for source code control, resize, then turn source code control back on. Thanks for the tip, sounds like a much easier work around.
Another workaround for this is <ctrl-m> only applicable if the VI is runable and if you allow your user to resize the collumns... (I din't knew this was SCC related :worship: )
Has anybody else seen this problem? If so is there a better workaround?Yep, and I just comment the lines out in labview.ini. I've reported it here and here and got replies from NI confirming that the next version/patch (I'm not sure which) will solve this.
Ton
-
-
How about the code capture tool?
It's already a fairly complete tool for what it does, but we could probably add some image editing functionality, drawing arrows, highlighting, commenting, etc.
I favor that, one bug is that multiple panes don't work.
However I'll try to upload a bugfree version of XControl Inheritance creator and I'd like to dare the community members to include method creation
Ton
-
Hi Marrco,
could you add your code?
I have Nero 6
Ton
-
I *knew* being proactive about beer would pay off one day -
Normally it pays off directly, like the next morning (this morning... felt like :headbang: ) And I promised a mate to take down his bathroom...
Ton
-
When I have to burn the CD the manual says I must connect an event (OnDoneBurn) to a method of the NeroDrive library
How do I get a reference/handler from a method ?
I think you need to create a callback event vi (right click-> create callback vi) And inside that VI generate the method?
Ton
-
Your code doesn't need to be finished to go into the LAVAcr - infact, code snippets are more than welcome,Posting like this just gets lost in the noise. It seems you have a steady development path. Let's see it in the CR. This is why the CR was created after all.
Allright I will post it into the CR, but I just noticied some issues with the 'new XControl options' (BTW the version on the net will not create those), but it looks like I left my usb-drive at work :headbang: , and the debugging steps I take are weird.
So I'll do some debugging on the code, and hopefully finish it early next week
Ton
-
Hi All,
here is an update for the XControl Inheritance Creator:
Download File:post-2399-1170369672.zip
Contained in a .ogp
After installation with VIPM, and a restart of LV, in the tools menu the XControl Inheritance submenu will show up.
Two options:
New and edit.
New will create an XControl prepared for the XControl Inheritance Creator in the current project
Edit will allow to edit the XControl Inheritance properties
Why didn't I post this into the CR?
It is not finished yet. I can't create methods, I will propose this as a challenge in mballa post.
Ton
Micheal, I couldn't add the .ogp file directly....
Micheal/Crelf I took the liberty to create a resource\Lavacr directory in the labview dir, since I will post this in the CR when the methods are available
-
Hi everybody!
I have an XControl that only has indicator functionality. However, when I place it on the front panel of a VI, it defaults to control.
So far, the only thing I have tried is to set the default state (RMB>>Data Operations>>Make Current Values Default) of the Container State cluster in the "Init" VI. This did not work.
Any thoughts, suggestings, solutions, or flames are welcome. :worship:
-H
I have been thinking about this as well,
what you could do if the format of the control is a 'control' display a message in the xcontrol that it is intended to be used as an indicator. It would be wonderfull if we could limit the state of the xcontrol into control or indicator
Ton
-
Problem solved
What was the solution?
Ton
Password protect editing
in User Interface
Posted
Pleas add your picture with LAVA and not external,
see this 'bug' thread
Ton