Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/15/2010 in all areas

  1. It might help to not think in terms of indicators and controls. I know this idea has been drilled into our heads since we first started working in LabVIEW but X-controls are a different animal. Instead try and think of an X-control items as having 4 states Development time Input mode Development time Output mode Runtime Input mode Runtime Output mode The Facade defines how the x-control with look and act for each state. If we use a numeric control as an example Increment arrows shown, White background, Data entry allowed No increment arrows, Gray background, Data entry allowed Increment arrows shown, White background, Data entry allowed No increment arrows, Gray background, Data entry not allowed So instead of trying to force the numeric controls by hiding and showing them I would instead change a numeric control's properties depending on its current state. Show arrows, Color background white, Enable Hide arrows, color background gray, Enable Show arrows, Color background white, Enable Hide arrows, color background gray, Disable I have found this way of approaching X-control design much less aggravating. Mark
    1 point
  2. You can put all three VIs into a single DLL and call them as different functions in that library. Your problem is the length parameter in the TCP Read. You only read 64 bytes, which would be sufficient for one double-precision value, but is not enough for an array. You need to prepend either the length of the string, or the number of elements in the array, to the string before you send it. On the receiving end, read that length and use that to determine how many bytes of data you need to read. Also, check the representation of your array constants; you do not need the conversion to DBL after the typecast.
    1 point
  3. I understood that part, I just don't understand why. I've modified my earlier example to use the Waveform data type, but you'll see that it doesn't faithfully represent what's been drawn. This is where you'll have to define how to convert X-Y data into a waveform (axis scaling and handling right-to-left pen movement, to start). Do you understand what I mean? main (1).vi
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.