-
Posts
6,203 -
Joined
-
Last visited
-
Days Won
111
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by Michael Aivaliotis
-
Name: JKI Please Wait Dialog File Submitter: LAVA 1.0 Content File Submitted: 03 Jul 2009 File Category: User Interface LabVIEW Version: 7.1 Version: 1.0.2 License Type: BSD (Most common) Potentially make this available on the VI Package Network?: Undecided Copyright © 2006, James Kring, Inc. All rights reserved. Author: Michael Aivaliotis Instructions: This code has been tested to run under LabVIEW 7.1.1. It will probably work on any newer versions but it has not been tested. Just unzip the code into any folder of your chosing and open the example called, JKI pwd Example.vi. This shows a typical use case where you want to pop-up a non-blocking dialog and display a message and updated text from a parallel running task. Features: - Can specify a limited preset amount of progress images via the "animation" selector - Can update the status message in real-time after the dialog has been launched. - Setting an animation value of 0 disables animation and displays only text. - Handles being built into an application - The dialog is not modal when run in the development environment however it becomes modal when built into an executable. Version History: 1.0.2: Renamed VI prefix from MNA to JKI. Added more documentation to diagram and VI descriptions. 1.0.1: Fixed bug where dialog was not centering on screen. Changed dialog behaviour so it updates position on screen before the front panel is open. 1.0.0: Initial release of the code. Click here to download this file
-
Currently the reputation system has some defaults which don't have enough levels or resolution. Plus they're boring. See image. Can anyone come up with some cool labels and define some levels for reputation? Make them LabVIEW-centric!
-
Yes, this was configured this way. We can allow negative but we won't.
-
Please upload small under 100Kb zip files
-
As you know there is a new file upload feature on the forums: The Flash uploader. This allows multiple file uploads to a post at the same time and it also has upload progress bars (very cool). This can be enable in your Settings: However it seems like some of us are having problems with the flash uploader. They get the following error: I'd like to know the extent of the problem: - Please enable the flash uploader (if not already enabled) - Try to upload a small file (a few kb) to this thread using the flash uploader. - If you have success then that's fine, don't post the reply. - If you get an error, then post the reply and specify what browser(w\version) and OS you are using.
-
Personal Image does not get resized on upload
Michael Aivaliotis replied to TobyD's topic in Site Feedback & Support
The problem was not the dimensions but the size on disk. The limit was set to 50Kb. I've increased it to 200Kb. -
In a few days hopefully. There was a reorganizing of the domains. The wiki will no longer be a LAVA subdomain anymore. It will be on a different domain with its own login.
-
Yes, this is done on purpose by the developers of the forum application (IPS). This data is refreshed hourly I think. This is to reduce calls to the database that stores the views.
-
Gary, we're working on importing the old content. In the meantime, feel free to start new topics.
-
Member's profile status
Michael Aivaliotis replied to Francois Normandin's topic in Site Feedback & Support
-
Member's profile status
Michael Aivaliotis replied to Francois Normandin's topic in Site Feedback & Support
This works the same as the facebook status. You can put whatever you like there. have fun with it. -
NI's put together a new section on their site called the LabVIEW Idea Exchange: QUOTE Link
-
QUOTE (Cat @ May 28 2009, 09:40 AM) So http://forums.lavag.org/SCRIPTING-IS-AVAILABLE-t14186.html' target="_blank">scripting is released while Cat is gone... Nice!
-
Alternative to "CMP compare two VIs.vi" for FRC
Michael Aivaliotis replied to joshxdr's topic in LabVIEW General
QUOTE (joshxdr @ May 29 2009, 07:29 AM) I think you should lobby NI strongly to get them to add these pro features to the version of LV for FRC, including integrated source code control. If we are trying to teach the students proper software engineering then we should give them all the tools. -
It's nice to see this finally come to fruition for sure. :thumbup: Thank You NI. I'd also like to see scripting discussions continue here on LAVA and hopefully y'all won't abandon us for the dark side. We have some excellent gurus on LAVA that were able to do cool things even with scripting locked. I can only imagine the possibilities now that it's been unleashed. As far as complaining... of course we'll still complain. Let's not forget XNodes and project environment integration.
-
A new article is up with info on how to unlock scripting: LabVIEW Scripting Here are the links for scripting download: LabVIEW Scripting API - Vista.zip (6.0 MB) LabVIEW Scripting API - WinXP.zip (6.0 MB)
-
Make starting a thread easier
Michael Aivaliotis replied to LAVA 1.0 Content's topic in Site Feedback & Support
This is an excellent suggestion Ton and something I have thought of myself. -
I saw this movie with my family. It will definitely spark a new generation of trekers. Great movie!
-
Getting LabVIEW Scripting out of the shadows
Michael Aivaliotis replied to crelf's topic in VI Scripting
Some news over here on this topic. -
NI has started a new group on their communities page called LabVIEW APIs. At the top of the page they announce that LabVIEW Scripting is on the way:
-
I'd really like to find out how they fold this t-shirt:
-
Getting LabVIEW Scripting out of the shadows
Michael Aivaliotis replied to crelf's topic in VI Scripting
This looks like the Patent for VI Scripting. SYSTEM AND METHOD FOR PROGRAMMATICALLY GENERATING A SECOND GRAPHICAL PROGRAM BASED ON A FIRST GRAPHICAL PROGRAM -
Calling other VIs to execution
Michael Aivaliotis replied to Pollux's topic in Application Design & Architecture
QUOTE (Pollux @ Apr 6 2009, 11:10 AM) Sorry, I must have been daydreaming when I wrote my suggestion. Yes, separate calls to the VIs but in separate parallel loops!