Home/ Questions/Q 648115
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T21:47:49+00:00

I’m not generally a GUI programmer but as luck has it, I’m stuck building

  • 0

I’m not generally a GUI programmer but as luck has it, I’m stuck building a GUI for a project. The language is java although my question is general.

My question is this:

I have a GUI with many enabled/disabled options, check boxes.

The relationship between what options are currently selected and what option are allowed to be selected is rather complex. It can’t be modeled as a simple decision tree. That is options selected farther down the decision tree can impose restrictions on options further up the tree and the user should not be required to “work his way down” from top level options.

I’ve implemented this in a very poor way, it works but there are tons of places that roughly look like:

if (checkboxA.isEnabled() && checkboxB.isSelected()) 
{
   //enable/disable a bunch of checkboxs
   //select/unselect a bunch of checkboxs
}

This is far from ideal, the initial set of options specified was very simple, but as most projects seem to work out, additional options where added and the definition of what configuration of options allowed continually grew to the point that the code, while functional, is a mess and time didn’t allow for fixing it properly till now.

I fully expect more options/changes in the next phase of the project and fully expect the change requests to be a fluid process. I want to rebuild this code to be more maintainable and most importantly, easy to change.

I could model the options in a many dimensional array, but i cringe at the ease of making changes and the nondescript nature of the array indexes.

Is there a data structure that the GUI programmers out there would recommend for dealing with a situation like this? I assume this is a problem thats been solved elegantly before.

Thank you for your responses.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    To clear this up, what I ended up doing was a combination of provided options.

    For my application the available open source rule engines were simply massive over kill and not worth the bloat given this application is doing real time signal processing. I did like the general idea.

    I also didn’t like the idea of having validation code in various places, I wanted a single location to make changes.

    So what I did was build a simple rule/validation system.

    The input is an array of strings, for me this is hard coded but you could read this from file if you wish.

    Each string defines a valid configuration for all the check boxes.

    On program launch I build a list of check box configurations, 1 per allowed configuration, that stores the selected state and enabled state for each checkbox. This way each change made to the UI just requires a look up of the proper configuration.

    The configuration is calculated by comparing the current UI configuration to other allowed UI configurations to figure out which options should be allowed. The code is very much akin to calculating if a move is allowed in a board game.

    • 0