-
Posts
2,767 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by Grampa_of_Oliva_n_Eden
-
QUOTE(eaolson @ Aug 20 2007, 02:09 PM) .taht yrt dluohs I ebyaM !TON .gnilleps ym pleh yam tI Neb
-
Thanks for starting this poll. I have a theory that can confirmed or contradicted by this poll (well not really). Ben
-
QUOTE(purehemp @ Aug 18 2007, 03:26 PM) A true understanding of all things is beyond our capabilities. We have to team up and trust each other to report on their area to the best of our ability. We are also responsilbe for evaluating what we see hear and read (unless we choose to reamain asleep, or is that "a sheep"). Ben
-
QUOTE(crelf @ Aug 17 2007, 08:50 PM) Its shows? Ben
-
QUOTE(crelf @ Aug 17 2007, 04:25 PM) What a bunch of bovine scatola ! Beat Christian to Knight of NI status and that will be impresive. http://forums.lavag.org/index.php?act=attach&type=post&id=6671 You may get Knighted by Jeff K himself. Even if you don't beat Christian to that mark but you beat me (and I'm still alive) I'll buy the :beer: to celebrate! Yes YEN the offer is good for you as well. Ben
-
Type conversion and inplaceness ?
Grampa_of_Oliva_n_Eden replied to LAVA 1.0 Content's topic in Development Environment (IDE)
QUOTE(Kevin P @ Aug 17 2007, 12:04 PM) The buffer re-use only is valid after a save 9actually a recompile) and if you had not done that, you may have questioned the lack of a buffer. The profile tool had a problem where it was not updating mem useage, but I do not remeber when that was fixed and what broke it. Sorry! Ben -
QUOTE(jzoller @ Aug 17 2007, 11:32 AM) That reminds me Stephen, is that were you got the "mu" from? Ben
-
Type conversion and inplaceness ?
Grampa_of_Oliva_n_Eden replied to LAVA 1.0 Content's topic in Development Environment (IDE)
QUOTE(crelf @ Aug 17 2007, 10:51 AM) showInplaceMenuItem=True For LV 7.0 and prior. It those versions you had to look at the buffer for each wire one at a time. Ben -
Type conversion and inplaceness ?
Grampa_of_Oliva_n_Eden replied to LAVA 1.0 Content's topic in Development Environment (IDE)
QUOTE(Tomi Maila @ Aug 17 2007, 08:36 AM) I'm leaning the same way. even an I32 > I32 feed from shift registers and stored in SR's still copies the data at its input. Similarly for string to U8's. Ben Note: This has changed with newer version of LV. See NI link for Christian example. -
QUOTE(TG @ Aug 16 2007, 09:20 PM) The local library serves my needs. If they are really good then I start begging my wife. Ben
-
QUOTE(dsaunders @ Aug 16 2007, 02:42 PM) I was trying to sit back and try to learn something but your last comment has me smiling becuase of two statements from people around me. One said "It is like using a bunch of "goto" statements". The other was my wife who has repeatedly said "Goto statements introduce chaos." Ben
-
QUOTE(Paul_at_Lowell @ Aug 9 2007, 12:54 PM) Wonderful suggestion Paul! I have only read the first 10 pages but the things I have read Stephen and Tomi write are already making sense. Maybe I'm not so "st-OOP-id" after all. :thumbup: Ben
-
Although arrays are not automatic, they can be done. THe example below illustrates a method that works on 2-d array. http://forums.lavag.org/index.php?act=attach&type=post&id=6635 Not Equal compare agregatres inside nested For Loop structure to get array of changed. Divide index by column count gives row and column. Index NewVal on you know what changed and what the new value is. Old value optional. Array size change detection is left as an exercise for the reader. Ben http://forums.lavag.org/index.php?act=attach&type=post&id=6636
-
Don't fight this battle alone. Let NI do their job. Get the local sales guy on the line and let him work on showing the higher-ups what LV and NI have to offer. If your oragnization wants to standardize LV out of the game, NI has a lot to loose. Make a phone call. Ben
-
Find out who and congratulate them in this thread. http://forums.ni.com/ni/board/message?boar...message.id=4022 Ben
-
QUOTE(Ben @ Aug 15 2007, 07:13 AM) Here is a screen shot of one of the sub-VI's after scrubbing to protect the inocent. http://forums.lavag.org/index.php?act=attach&type=post&id=6627''>http://forums.lavag.org/index.php?act=attach&type=post&id=6627'>http://forums.lavag.org/index.php?act=attach&type=post&id=6627 This construct was natural for me when I started out and was still thinking about pushing things onto stack and poping them off. It also has a natural dual priority scheduling feature in that if you insert at the head of the queue those states pre-emt others and low priority can put at the back of the queue. When we only had a single thread and were trying to do more than a PC wanted to, these were useful. It just strikes me that thinkinga bout pre-empting and priority of execution is falling by the wayside now that we have almost 100X the CPU from just 5 years ago. So you still use this type of structure? Ben
-
QUOTE(shoneill @ Aug 15 2007, 03:42 AM) A code construct that maintians an array of "States" in a shift register and pops the top state of the stack and executes same. Any state can push other states onto the stack before they complete. All state involved in the application are implemented as cases. It only uses a single loop. Becuase the state transtitions are only established while the code is running, it is impossible to diagram what will happen in what order. States will execute in the oder they are removed from the stack but because states can "preempt" other operation already on the stack, you have to repeatedly check what is on the stack to understand where it is going (possble if the stack is an array, impossible if the stack is in a queue). And then if you decide something bad happened in an earlier state, there is no way to trace it back. I'll see if I can get a screen shot it this 40-50 state monster that prompted this Q. Ben
-
After some of my fellow wire workers were looking at a very complicated QSM application I explained that architecture was fine if you have spent your whole life doing assebly programming and you did not want to change the way you design applications. With LV's multi-threading, it seems to me that there is no need to use one of those undocumentable monsters. So although I have already instructed them to "never develop anything life that" I thought I may want to do a sanity check with Y'all. So.... Are the days of the QSM behind us? Please share your thoughts, and I will sit back and learn. Ben
-
QUOTE(LV_FPGA_SE @ Aug 14 2007, 03:20 PM) Don't both of those methods suffer from the "NI redefined the data format" issue that complicates reading files writen in earlier versions of LV when upgrading? Ben
-
typedef and element cluster order
Grampa_of_Oliva_n_Eden replied to LAVA 1.0 Content's topic in LabVIEW Bugs
QUOTE(TG @ Aug 14 2007, 02:03 PM) I think I would like LV to make all of the explicit ref's invalid to get me to look at what I may have missed. So I guess I am disapointed that it does not do so already. I guess the only thing we can do is submit it as product suggestion and hope. Ben -
QUOTE(Puzzlemaker @ Aug 14 2007, 01:24 PM) Please let us know how things work out. There may still be other solutions, but first try the OpenG approach. Ben