Strange issues with 5.0.18

I'm just now resurrecting a cockpit project that never really got started. I downloaded and installed FS2Phidgets 5.0.18 and ran into some issues when I hooked up one Phidget board for a quick test to see if everything was working.

First, my IO 0/16/16 board I bought 4 years ago shows up fine, but I couldn't get any components on the board to show up in the GUI until I loaded the 8/8/8 emulator and then switched back to my 0/16/16.

Second, The "Component/FSVariable/Lookup section in the upper right of the GUI is sized wrong and I can't access any dropdowns (to assign an FS variable, for example). Some of the other GUI elements seem strange too.

It strikes me this might be either a Windows 7 issue or a screen resolution issue where the GUI isn't resizing properly. I'm running at 1600x1080.

I took a couple screenshots of the GUI. They're at:

http://www.hastyfilms.com/files/FS2Phidgets-1.jpg
http://www.hastyfilms.com/files/FS2Phidgets-2.jpg

Any ideas? Kinda unusable like this...

--Jim

Well, it is useable after all. I figured out that even if I can't see the drop down arrows to the right I can still click on the box and get the drop down list of variables.

It's still kind of messy though...

--Jim

Jim,

I am using a laptop as my development pc, that is 1024 X 768, I use a 19" LCD to run software in my hanger. I have made a number of fixes and upgrades to 5.0.19. A few folks are trying those out. Will be releasing that version shortly. Below is short list of fixes and upgrades:
5.0.19 03/18/2010 Program dumping when deleting circuits.
03/20/2010 Program dumping when using 8 byte FSVariables.
03/21/2010 Add calibration button to set travel on servos and sensors.
03/22/2010 ZeroWhenOff property also for Digital FSVariables.
03/23/2010 Performance improvements.
03/23/2010 Ignore FSVariables that gives a read error. Prompt and log error.
04/06/2010 Some components assigning to incorrect circuit when project loads.
04/06/2010 Internal FSVariable for passing value and state.
04/07/2010 Digital Output FlashRate property.
04/14/2010 Include date in log entries.
04/18/2010 Reposition and drag-and-drop functionality.
04/21/2010 Buttons to align and arrange components.
04/25/2010 Generate all components for a Phidget card.
05/02/2010 Import circuits from another project.
05/03/2010 Discontinue circuit-as-template component.
05/04/2010 Copy circuits function.
05/07/2010 Timer component.
05/12/2010 Remove Enable button.
05/13/2010 Write to FS bug.

Regards,
Alan

Thanks Alan. Do you think all the issues I am experiencing are because of screen resolution? That explains some of the GUI elements being in the wrong place but what about the Phidget components not showing up for my board until I loaded the 8/8/8 emulator?

Before I forget, thanks for this wonderful application. You've made it simple to build a cockpit for people that don't know how or don't want to write code (I fall in the latter category. I know how, just don't want to...the old "why reinvent the wheel" thing, and you've built a nice wheel!)

--Jim

I seem to recall I had same problem you described with the phidget drop-down list not populating correctly. Fixed that in 5.0.19

Something I noticed with your initial post on this thread.
The text is all narrow. I have seen other posts like this on other threads.
Did you post that from system that was having resolution problem?

I'm posting from the same system running FS2Phidgets, but all the forums look OK to me.

--Jim

I noted on various forums that people were experiencing resolustion problems with W7. Especially with Dell and Nvidia graphics cards. Suggestions ranged from setting Desktop to Windows Classic and:

1. Right click on desktop

2. click "screen resolution"

3. Click the blue text - "make text and other items larger or smaller"

4. Click on - smaller - 100% (default)

5.0.19 is available for download.

btw, regarding the narrowing problem you highlighted.
I saw on some other Windows7 related forums that you can try setting short compatibilty setting to WindowsXP.
That may help.
Let me know if still problem.