UI: FPX Data / Settings Needs Clear Separation

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   The current component data entry dialog does mix and match data from the FPX and from the Preference file.
- It is not clear which fields are part of (and will be stored in) the fPX file, which fields reflect program wide settings and which fields reflect Component Type specific settings
- Some tabs have a restore default button, other don't.
- It is not clear which values are modified from de defaults (both for settings and fpx data).

I would recommend re-arranging the tabs as following:
Component (All FPX data)
Dimensions
Footprint (Use manufacturer's recommended dimensions)
Preferences (All Preference Data)
Console (Units?)
Rules
Drafting
Component
Terminal
3D Colors
Calculation
Errors/Warnings
It should be clear what happens with the preferences fields, so either:
Make them read-only
Add a message "Changes to these fields are not stored in the FPX library"
Add a button save changes to preferences
Add a button go to preference page
I think the tabs with preferences should be identical from the ones
 in the preferences dialog. Also note that the terms 
Preferences/Settings/Setup are used throughout the tool to refer to the 
same thing. This is also confusing.

In the preferences page, every field that is modified from the system defaults should be highlighted with a button to restore that individual field (instead of restore all).

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Joris-Hiber Members Profile Send Private Message Find Members Posts Add to Buddy List Active User Joined: 24 Oct 2018 Status: Offline Points: 12	Post Options Post Reply Quote Joris-Hiber Report Post Thanks(0) Quote Reply Topic: UI: FPX Data / Settings Needs Clear Separation Posted: 21 Nov 2018 at 3:37am
	The current component data entry dialog does mix and match data from the FPX and from the Preference file. - It is not clear which fields are part of (and will be stored in) the fPX file, which fields reflect program wide settings and which fields reflect Component Type specific settings - Some tabs have a restore default button, other don't. - It is not clear which values are modified from de defaults (both for settings and fpx data). I would recommend re-arranging the tabs as following: Component (All FPX data) Dimensions Footprint (Use manufacturer's recommended dimensions) Preferences (All Preference Data) Console (Units?) Rules Drafting Component Terminal 3D Colors Calculation Errors/Warnings It should be clear what happens with the preferences fields, so either: Make them read-only Add a message "Changes to these fields are not stored in the FPX library" Add a button save changes to preferences Add a button go to preference page I think the tabs with preferences should be identical from the ones in the preferences dialog. Also note that the terms Preferences/Settings/Setup are used throughout the tool to refer to the same thing. This is also confusing. In the preferences page, every field that is modified from the system defaults should be highlighted with a button to restore that individual field (instead of restore all).



Tom H Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 05 Jan 2012 Location: San Diego, CA Status: Offline Points: 5716	Post Options Post Reply Quote Tom H Report Post Thanks(0) Quote Reply Posted: 21 Nov 2018 at 11:42am
	We are in the process of a 100% complete rewrite in V2020 using C# code. The Term "Preferences" is changing to "Options". There are no tabs in V2020. They are being replaced with expandable windows as the UI is being upgraded from Visual Basic to Windows Presentation Foundation (WPF). In January, we'll invite you to a webcast to see the new V2020 layout. In the meantime, all programmers are busy with V2020 progress and V2018 is strictly in a "Bug Fix" mode. We do not want to touch V2018 as it will soon be phased out and our goal is to keep it "Bug Free" for those users who wish to continue to use that version.
	Stay connected - follow us! X - LinkedIn

Joris-Hiber Members Profile Send Private Message Find Members Posts Add to Buddy List Active User Joined: 24 Oct 2018 Status: Offline Points: 12	Post Options Post Reply Quote Joris-Hiber Report Post Thanks(0) Quote Reply Posted: 21 Nov 2018 at 1:45pm
	C# sounds like a good idea :) Yeah it’s not critical and I don’t expect this to be changed immediately I just wanted to share my suggestion. Looking forward to the 2020 release!

Tom H Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 05 Jan 2012 Location: San Diego, CA Status: Offline Points: 5716	Post Options Post Reply Quote Tom H Report Post Thanks(0) Quote Reply Posted: 21 Nov 2018 at 3:04pm
	The V2020 rewrite will offer much more flexibility to add new features and change existing features. The new code will be highly optimized for the next generation PCB library automation. Moving code from Visual Basic to C# trades 100 lines of code to 1 line of code. V2020 will also have schematic symbols with a split screen to show both the symbol and footprint side by side.
	Stay connected - follow us! X - LinkedIn