pandaman

Hello fellow LabVIEW wirers, I am "renovating" a relatively large program I have made in the past with new features. I am adding alot of buttons in the process, which I plan to control with event cases. Some buttons lie directly on the front panel, while some are in a tabbed interface (a few buttons for each tab). On the block diagram, I have an event structure surrounding the case structure (for event timeout=100ms) which handles events for the buttons outside the tab. The case structure is for the tabbed interface. I am thinking of either placing a set of nested event structures (for each case in the case structure) to handle the tabbed buttons OR make the outer event structure handle these buttons. Which is more CPU-time efficient? I would think the nested version (since the outer event structure would not have to check for events that do not apply for all tabs), but since the nested one would be in event case timeout, I am uncertain. If my description is unclear :headbang: , I can upload an example. Thanks, Mayur

Yep.. after adding stuff to the .ini I was able to edit the actual plot bounds. Thanks everyone for your help!

Hello once again, I am having trouble coding a way for the user to control the "plot area" size (which I interpreted as the black gridded area) without changing the overall size of the graph. My reasoning is in regards to aesthetics; I don't want a gap between the graph and a decoration. If this cannot be fixed, is it possible to programmatically control the size of a decoration? I doubt it myself because there are no block-diagram components for decorations. I have attached a sample VI to further illustrate my intentions. Yes the outcome is not significant in importance but I have a pet peeve about it Thanks in advance :worship: Mayur Download File:post-2549-1149514836.vi

Hello one and all (again), Is there a way for the user to save the state of one's program (i.e. the values of a control) to a file without manually writing values to a spreadsheet manually? It would be kinda useful in the event that a buncha settings are tweaked and the user just wants to quickly recall them later. Muchos gracias, Mayur PS: please do not be offended by my post icon, I wont use it again!

That movie was the s*** - I mean the best ever :thumbup:

Very clever "underlying truth" :thumbup: in your time reversal algorithm Hope my comments are slightly more lucid than those of al.... allright time to get back to work :ninja:

Hello one and all, I am trying to solve for a root using Find All Zeros of F(x).vi (Functions>Analyze>Mathematics>Zeros), but I am getting an answer that is out of my specified bounds (see attachment). I could probably check for this in my program, but why isn't this function detecting this? Thanks, --Mayur P.S.: O'yea I already tried using a different algorithm and different step type, but the answer was the same. I go a root at x=.69 even though my start bound limit was .73. Oh and I am using Labview 7.1 in this instance.

That's horrible :thumbdown: . That is why I am a vegetarian :thumbup:

Hello one and all, I am trying to solve for a root using Find All Zeros of F(x).vi (Functions>Analyze>Mathematics>Zeros), but I am getting an answer that is out of my specified bounds (see attachment). I could probably check for this in my program, but why isn't this function detecting this? Thanks, --Mayur P.S.: O'yea I already tried using a different algorithm and different step type, but the answer was the same. I go a root at x=.69 even though my start bound limit was .73. Oh and I am using Labview 7.1 in this instance.

Whoops... :headbang: my bad.

If removing overlap and increasing times between refresh do not fully recover CPU speed, try investing in a graphics card. GCs almost always have a separate processor and memory dedicated to graphic alone. As a result, you main processor and RAM will be reserved for computational calculations, and the graphics card's processor and memory will deal with graphics. Mid-range cards usually run for around $100; however, you may find a decent lower-range card that fits your application for much less. I suggest buying a card that has at least 64MB memory and a core clock speed of 175MHz. This may not be of help if you have no available PCI/AGP slots, or you are under a strict budget . I am sure, though, that following information from other members' posts will prove much more help in solving your dilemma :thumbup: since they are software fixes. This is more of a last resort :ninja: . --Mayur

Never had that problem w/ 7.1

Hello one and all, The current project I am working with requires a UV lamp that emits a very focused and narrow beam of UV light. The diameter of the beam should be within one micron or, if possible, adjustable between 1 micron and 250 nanometers. It must be focused enough to emit this diameter of light when fixed above the specimen 10 cm above. The wavelength of the beam is not a concern yet. Any help or ideas are appreciated. Regards, Mayur

Nice! :thumbup: The only problem I have (a very minor one at that) is that the point where drawing occurs is above and slightly to the right of the cursor (see picture).

Yeah, I should of done that, but all you needed was kel's code, since I used those subvi's. No worries, i'll just provide the lib. Download File:post-2549-1124897010.llb