Situation

I'm designing desktop software that is meant to be as easy to use as possible, without annoying power users. In other words, I have a very dispersed range of users, with no way to test the audience (new product). Also, even though it's desktop, I'm designing it to be non-resizable, so it can't use more screen space than 800x600 (lowest reasonable screen resolution).

I've come across a common problem where I want to offer the user a choice between a small set of options, but each option must be configured separately. A Step-By-Step Wizard walkthrough works, but is highly annoying because it adds too much navigation to be used often. So, ideally, I need it to fit in one view.

Using JavaFX if that's important in any way, with FXML and no external libraries. Also, I'm the sole developer (and not a UI/UX expert).

Example

Part of my software involves automation. So the user sets up tasks to be run under certain conditions. Each task contains a lot of data, so I keep task configuration in a separate view from the "list of tasks". When configuring a task, though, the user is faced with a similar option of adding a component, but the component is a bit small for it's own window.

Let's use a Stop Condition, which is an indication of when the task should stop.

My current solution:

In this example, the user is able to select between Condition Types. Once a condition type is selected, the configurations for that specific type will be enabled (turned editable).

The problem is that this is a hard UI to extend if I need to add a condition type, and it takes up a lot of space.

Other Ideas

• Instead of the Condition "Options" being always visible, turn the RadioButtons into a ComboBox selection and have the Options for each Condition turn visible when the corresponding Condition is selected.
• Replace the Radio Buttons with a ComboBox for selecting the Condition Type, and then adding a new form for each Condition Type for the corresponding options.

I dislike these because making UI components appear and disappear might be confusing. And adding even more windows can be overwhelming.

My Question

How do Desktop Applications deal with choices such as this? Am I focusing on the wrong point or am I simply making the best of my circumstances?

*Note: Please keep in mind that I have limited screen space and very little support/experience for animations that might ease user-confusion.

EDIT: Here is an answer that suggests my solution is a good one: What is the best way to gather optional data using radio button groups and drop-downs?