New Version Suggestions

[erblock]

1. Add a readable data member to the Pot object that pulses whenever it's value changes (local input value changes are most critical in my applications).

You can use increment, decrement members for tracking some changes, but there is nothing to track "Enter new value for ..." inputs which change the pot value.

[Mike@DTSI]

Labview runs in linux: http://sine.ni.com/nips/cds/view/p/lang/en/nid/2541

I suspect people who complain windows crashes too much need to read a little more about configuring systems.  Keep in mind the operates need to be trained as well.
We have 2 windows 2000 systems with uptimes of over 1 year at a time (these systems still run today!) only restarted for patches and updates.
We have 1 windows 2003 servers with 2.5 years uptime (our file/fax server).
My system (windows xp) has been running (error free) for 3 years.

Linux has its place, and this is one of them, but i myself has seen linux crash as well 🙂

SUGGESTION:  Stop corrupting the database on a bad Lookout shutdown. 

[erblock]

Dreaming now.....

1.  Add object and expression security parameter which allows/restricts object repositioning within panels while in run mode.  So on any given panel, there would be objects/dispays that are fixed (as all objects/displays in run mode currently exist) and others that, depending on username or user level permissions, could be repositioned (and saved in that position...ideally) on the panel.

Anyone can reposition panels in run mode....  I want some people to be able to reposition some items on any given panel!  Not much ot ask now....

[Mike@DTSI]

As erblock brought up something similar.

Make the parameter on graphical object able to read files from other directories.

ex.  Animator.Grfsource = "c:\My Dir\My Pic.jpg"

Mike

[erblock]

1.  Log-10 scales for Hypertrends.

2.  Also, improve grids on hypertrends  (grid line width/sharpness adjustment).  If fine adjustments of grid line weight (points or pixels) is not reasonable....  Maybe a "boldness" adjustment of 2 or 3 steps along with the existing grid shade would produce reasonably improved capability.  Fine gridline capability would be of even greater importance on log scales.

3.  An added bonus capability:  Adjustment for Hypertrend trace line thickness (particularly usefull on log scale traces of for traces that do not change much (heavier linetype = more visible trace)

Message Edited by erblock on 02-07-2008 01:55 AM

[erblock]

1.  A group of objects to make up an instrument display should all scale together when grouped.  As it is now (detected so far...), text does not scale and pot increment buttons do not scale.  This is important when refitting screens to other monitor resolutions.  Digital pot representations, pushbuttons, pipes, plates....all scale great when grouped and scaled together.  Please consider allowing all grouped objects on a display panel (including text fonts) to scale in this manner.

Note: I am currently scaling proportionately, that is with corner draging of grouped display objects.  I do not expect to properly scale text from a 4:3 screen to a wide screen or vice versa, although it would be really cool if you could manage that! 😉

[erblock]

2.  Expand the recipe object concept to fit other data inputs.  I am using the object to input routine roving check data for display in Lookout.  Please allow cells beyond row 1 and column A to contain text.  This will allow comments to accompany numeric data within the "recipe" spreadsheet.  Suggestions???

[JPhillips]

Add "visible" data member to "text entry" object so that you can connect it to a switch and display different text when needed on a panel.

[erblock]

Just another plug to get all graphical objects to be re-size friendly.

My latest example is for touch screen application:

1.  The Hypertrend object is one of my favorites...., however, the size of the top scroll, date, start/stop icon (all part of "Button Bar") including the text parts, as well as the "bottom bar" with the time display...  Have not scalable features.

This is really important for touch screen systems, where you need to make things reasonably large to allow fumble fingers to make adjustments, as well as to make things readable from a longer distance.

Basically, as it stands now, the Hypertrend object is only usable for a normal, fairly low resolution (1024 X 768 or less) in a touch screen scenario.

2.  When analysing historical data interactively on a Hypertrend, the pop-up data-display box cannot be re-sized to allow more than three trace values to be displayed simultaneously.  Additionally, the text size in the display cannot be adjusted.

Please consider these aspects of the GUI  justly when budgeting time for Lookout improvements.

Cheers,

Ed

[erblock]

Related to the first post in this thread.

Allow configuring the existing, single Lookout executable window to open on a specific display when using dual or quad video setups.  Right now, it will only go to the primary (#1) display and cannot span multiple displays

The ability to configure the single Lookout executable window to span multiple displays would be a real bonus, especially if NI is unable to return to the multi-Lookout application running simultaneously scheme of pre-5.0.

Of course, the ability to control these diplay characteristics/position at application startup is critical.

Message Edited by erblock on 02-25-2008 02:54 PM