Jump to content

Yuri

Members
  • Posts

    8
  • Joined

  • Last visited

    Never

Posts posted by Yuri

  1. Problem: Standard LabVIEW-controls demand the big number of mouse button pressings "for navigation". Ergonomics say: "It's irrational ..."

    Solution: It's necessary to have control with easy navigation and editing.

    The properties of the (numerical) table:

    1. Two types of navigation for table: (A) - use of mouse moving, (B) - use of keyboard.

    2. Use of "lock-cells" with "not-edit" data.

    3. Diagnostics of errors (non-numerical data) and search of cells with errors of data.

    4. Scheme of using of other data ("external" controls) by means of references

    add: This control will be used in my project. Any remarks, versions and your corrections -> important for me.

    Download File:post-4964-1150931965.zip

  2. Hi all,

    If we have the link on xcontrol, then we have access to xcontrol-property and xcontrol-method. However if for any subroutine make control-input="xcontrol referency", then in subroutine will be accessible only standard property and methods. Individuality xcontrol will be lost. There can be it a mistake, or can be - ideology. In any case it reduces convenience.

  3. Please see attached mod of the previous.

    I used "defer Panel updates" to be able to measure the updates w/o screen update times.

    Repeated runs show that the terminal will SOMETIMES (do a bunch of ctrl-r) run as fast as the local.

    The "nightmare" is now faster because I moved the reference node outside the loop.

    Nice topic!

    To quote one of my old girl friends daughter "I want to go fast Mommy!"

    Ben

    Download File:post-29-1147353606.vi

    Ben, thanks for "defer"-property. I did not know (!) it. It is bad :)

    But the common conclusion remains - use of reference slows down (noticeably) speed of execution :( ((

    If to think: It was always (and in old versions, for example LV5.1): use of property (== linked reference) for change of graphics-attributes is Nightmare #2!

    For me it: "perestroika" :) of ideologies of my programs :(

    Probably, it is time to write new recommendations for LabView-programmers and to make tests for "get/set" for different types of data (for example array of clusters), and for converts of data- types (variant and more).

    NOTE: you write: "The" nightmare " is now faster because I moved the reference node outside the loop "

    Excuse, but the position of reference can be any. Inside of cycle any way the copy of reference is created (automatically). Check up, please, timing does is not change.

  4. Yuri,

    Unfortunately, I can't run your code (I'm on LV7.1), but I am quite surprised by your tables. Do I understand correctly that your results are consistently better when you pass data via a local than when you wire directly into a terminal?

    I am quite surprised by this, especially considering the following from the LabVIEW

  5. 1. Sorry, this test incorrect. For example look: the test for graphic method=GRAPH "more slowly" than " XY GRAPH ". But GRAPH-method use N-poits, XY-GRAPH-method use 2*N-points. hmm, it is a surprise...

    Say to your colleague (Vito:): please, remove from the diagram "cancel button " and "wait"-function

    2. Profile? There is no hope :( - he is mistaken as the PC-timer.

    Please, also read LabVIEW Help-> Profile Performance and Memory Window:

    " Display-... Display can be inaccurate if you do not right-click the control or indicator and select Advanced

  6. I do not know how "correct" my method is but I'll share it for the sake of conversation.

    I deal with the three color components like the like they are vectors in color space.

    To get a gey scale representation I take the square root of the sum of the three components squared and then divide by the max possible vector length (sqrt [ 3 X 255^2]).

    the result of that value becomes the new R, G, and B values.

    Ben

    Grey shade GREY it RGB with components (GREY, GREY, GREY). Therefore the algorithm (formula) for three numbers (R, G, B) and GREY is important. Frequently use (processing of digitalimaging) formulas (http://neuroface.narod.ru/files/mahfoudh_autoref.pdf)

    (1) grey=0.3*R+0.59*G+0.11*B

    Or

    (2) grey = (R+G+B)/3

    (if R, G, B, GREY = [0,1])

    Results are lower.

    0-initial picture

    1-calculation under the formula (1)

    2-calculation under the formula (2)

    (since I lazy my example uses interpolation from labview above :) )

    post-4964-1147217943.gif?width=400

  7. hi everyone i have a problem here which i really cant solve. this programme actually is my sequence programme but i need to add a stop button to stop the operation at any one of the flat sequence i tried but cant solve. anyone knows please help me. THANKS in advance :worship:

    The most simple way - to change the status of the stop button and add its local variables in sequence.

    post-4964-1147174424.gif?width=400

×
×
  • Create New...

Important Information

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