Michael Aivaliotis
-
Posts
6,217 -
Joined
-
Last visited
-
Days Won
120
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by Michael Aivaliotis
-
-
Don't use any type definitions inside your class data.
I'm not sure I'm following what your final implementation looks like. You're letting LabVIEW load the object with the binary read function and then fixing your index if it's bad? Is the index a scalar value that requires some logic to determine its value? I would probably use the class version number to determine what code to execute on the data to fix the index. At the end of the day, you still need to do some "fixing".
When I've had to do this. I use a multi-stage sequential conversion routine. based on what version I'm reading. So if you have 3 versions of your file then you would do 1->2->3. Needing 2 conversion routines.
I've stayed away from using the class versioning system for saving object data because I tend to use typedef clusters in my objects. Ya, I know, bad - bad Michael. I'm slowly trying to ween myself from this habit.
-
1
-
-
All of us here on LAVA wish you a speedy recovery.
-
1
-
-
The book describes how I used to program like 10 years ago. I later migrated to OpenGoop, Very out of date. It's very light on the OO concepts as well. Native LVOOP is the only way to go moving forward and this book doesn't help you get there.
Not saying you can't use the methods described, but why would you when there are better ways.
As far as the printing, I was lucky to get the first one out in 2003. So quality was excellent.
-
Not specifically from this board, necessarily, but I'm looking for ways to build my skills. I'm the only person who uses the language at my company and I get around well enough to run our test sector, but if I'm going to move up or on, I need to get better.
Does NI sponsor user groups? Are there real-world LAVA lounges? Any pointers in the right direction are appreciated. Thanks.
Where are you located?
-
I just reported it to Invision. Thanks.
It's apparently a known issue that is going to be fixed in an upcoming release. Thanks for reporting it.
-
I just reported it to Invision. Thanks.
-
There are two icons which you can use to link back to lava. Please link directly (do not copy to your site) to these icons:
http://lavag.org/uploads/links/lava.png (80x31)
http://lavag.org/uploads/links/lback-lava.png (88x31)
These can be used by any other blogger or website as well.
-
Daklu, any chance for you to attach your code instead of just images?
-
I've seen this delay before, but not LV2010. I've seen this in LV2009. It happened only in one project of mine. I tried several things to debug it and came to the conclusion that it was due to the complexity of the VIs and not the entire project. Editing some VIs was faster than others.
Here's a video showing this:
I do use the SCC with LabVIEW (Visual Source Safe). What do I have to do, disable integrated SCC in LabVIEW? It seems that there are so many don't do this or don't do that (don't have the project open, don't use 32-bit PCs, don't use the Find feature, etc.) in order to have LV2010 work properly.
Bruce
I don't know what all you guys are talking about. All of this feels like superstition. Don't walk under a ladder or else you get bad luck. Gimme a break.
-
In general I agree with you. However, LV disallows more than just editing when a vi is locked. I can't copy-and-paste code or controls from a locked vi to the vi I'm working on. I can't right-click >> Find All Instances of a locked vi. (That one really irritates me.) Personally I enable those options on my dev computers, but I think it's a tougher sell to make it a default setting.
I agree with you too! Why can't we prevent editing (changing the code) but allow copying and find all instances etc?
-
(Continuing the Cross Posting)
Forget I mentioned SCC, as this really isn't a SCC issue. In general, ask yourself this question: should you be able to edit a read only file without explicitly setting it to edit mode? I think the answer is no.
I agree with crelf.
-
@Michael: Do you have a link to LAVA CR etiquite? My code is deep in development and has some horrific syntax and improperly named VIs and controls. Is "unreleasable" code ok to release to CR?
I assume it is easy enough to "upRev" when available. Some have suggested I Blog about my Lunar Lander antics but I'm not sure it is blog worthy... maybe worthy of a thread here? dunno...I am interested in having my code critiqued but I'm afraid the easy ugly gets in the way.
I just want to see it. You can just attach it to the current thread as a zip file. Whatever you have.
Edit: I just moved this thread to a different subforum.
-
Not the Block Diagrams you're looking for:
-
You can't imagine how happy you made me right now...
I'd love to see this implemented.
Is it possible for us to see some of the code? What are your plans for this. Perhaps post it on the LAVA CR?
-
It's all about what you're used to. I've spent my entire life in central and south Texas. I have no clue how to drive a vehicle when the roads are icy, and I don't even try. And I'm not afraid to admit it.
Good idea Darren.
-
Stupid question. Why does your plugin class have to be in a separate project? Your statement: "To make it easier for people to add their own functionality to the program without having to dig into the full project" is not clear to me.
Which class is the reusable component? Classes are libraries and libraries are by design meant to be reused.
-
So what's the real problem Ton? Do you have a website that's causing NI some problems?
-
Thanks to Tomi for introducing me to this:
-
... similarly I don't pay attention to the all-out LabVIEW supporters who refused to acknowledge its limitations and weaknesses.
True, LabVIEW has limitations. That's why we're all here pushing the limits right?
It's also true that you can have a successful lifelong career in LabVIEW and even run a software company that uses LabVIEW to its core, without ever having to touch a sigle line of text code. Oh, and it's fun too.
The nice thing about all this: I never even once throughout the years doubted my decision to base my career around LabVIEW.
-
2
-
-
The thing with LabVIEW is, either you "get it" or you don't. Those that don't will never change, so don't bother. Our job is to try and find those that "get it" and help them grow.
Hmm, that sounds like a religion.
-
Featured sounds like 'studied and selected' (perhaps paid?), but it looks like it incorperates the last addition. Is that correct?
Ton
For now it's stuff that I feel needs to be featured.
-
2
-
-
Jon,
Please can you edit your LV Assistant page so that the link for the Icon Editor API actually looks like a link. Only when you mouse-over does it become apparent it is a link (this is in Chrome). I had to search the internets to try and find it and finally, like Jim, stumbled on this page.
Thanks!
and again, great tool :-)
For some reason, links on the LAVA CR pages look a little different. I'm working on fixing this.
Edit: This is now fixed. The links on the LAVA CR match the look on the rest of the site.
-
I hate, hate hate hate the new probe windows....
The new Icon editor is next on the list.
I'd like to add a bit more to this so I don't sound harsh. I like the idea of overhauling the probes and the icon editor. It's a step in the right direction. They just both need improvements to make them really useful for me and not get in the way of my workflow. They're not there yet.
-
I hate, hate hate hate the new probe windows....
The new Icon editor is next on the list.
Serializing Objects
in Object-Oriented Programming
Posted
I dunno man. It sounds like you need a database instead of a file. Just load the data you need based on a query. But that's a whole other thread perhaps.