Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
Need the latest SmartSDR, Power Genius, and Tuner Genius Software?
SmartSDR v3.4.24 and the SmartSDR v3.4.24 Release Notes | SmartSDR v2.9.2 and the SmartSDR v2.9.2 Release Notes
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes
Power Genius XL Utility v3.7.32 and the Power Genius XL Release Notes v3.7.32
Tuner Genius XL Utility v1.1.16 and the Tuner Genius XL Release Notes v1.1.16
SmartSDR v3.4.24 and the SmartSDR v3.4.24 Release Notes | SmartSDR v2.9.2 and the SmartSDR v2.9.2 Release Notes
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes
Power Genius XL Utility v3.7.32 and the Power Genius XL Release Notes v3.7.32
Tuner Genius XL Utility v1.1.16 and the Tuner Genius XL Release Notes v1.1.16
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Disable DAX button when Monitor button is Enabled
Jay -- N0FB
Member ✭✭
I'm not sure if this should be categorized as an Idea or a Problem, so out of caution, I'm posting this as an Idea.
Much confusion occurs in the GUI when presenting the user with invalid combinations. Such apparent invalid combination is when both the Monitor and DAX button are enabled. Whether this is a bug or an intentional design, both DAX and Monitor features are currently mutually exclusive of each other during operation.
My recommendation would be: If the Monitor button is enabled and the user presses the DAX button, programmatically deactivate the Monitor button. Vice versa, if the DAX button is enabled and the user enables the Monitor, programmatically deactivate the DAX button.
Good GUI design prohibits presenting the user with an invalid selection or an invalid combination of selections.
Much confusion occurs in the GUI when presenting the user with invalid combinations. Such apparent invalid combination is when both the Monitor and DAX button are enabled. Whether this is a bug or an intentional design, both DAX and Monitor features are currently mutually exclusive of each other during operation.
My recommendation would be: If the Monitor button is enabled and the user presses the DAX button, programmatically deactivate the Monitor button. Vice versa, if the DAX button is enabled and the user enables the Monitor, programmatically deactivate the DAX button.
Good GUI design prohibits presenting the user with an invalid selection or an invalid combination of selections.
0
Comments
-
I'm with you on that, Jay. It took me a while to figure out that DAX and MON were mutually exclusive.
I would still like to figure out a way to monitor with DAX on, maybe through the PC.
1
Leave a Comment
Categories
- 20.1K All Categories
- 189 Community Topics
- 2K New Ideas
- 390 The Flea Market
- 6.7K Software
- 5.7K SmartSDR for Windows
- 109 SmartSDR for Maestro and M models
- 277 SmartSDR for Mac
- 210 SmartSDR for iOS
- 208 SmartSDR CAT
- 143 DAX
- 332 SmartSDR API
- 8.2K Radios and Accessories
- 6.7K FLEX-6000 Signature Series
- 682 Maestro
- 37 FlexControl
- 808 FLEX Series (Legacy) Radios
- 576 Genius Products
- 323 Power Genius XL Amplifier
- 208 Tuner Genius XL
- 45 Antenna Genius
- 174 Shack Infrastructure
- 113 Networking
- 286 Remote Operation (SmartLink)
- 109 Contesting
- 455 Peripherals & Station Integration
- 105 Amateur Radio Interests
- 723 Third-Party Software