Configuration Files not loading properly
I'm just getting started with developing different configurations and writing scripts so I have two different configurations set up in BruControl, one for writing and testing the scripts and another for the brewing process itself. When switching back and forth between configurations, the script area does not reload properly, it comes up blank (no script showing). The name of the script still shows up on the left as paused but no lines of code are showing up in the editing area and no data is showing in the variables and output area. I have to restart BruControl each time I change configurations to get the script area to properly display the script. I noticed this happens in both the original build of BruControl (v 1.0) and the new beta version (v 1.1).
As suggested, I tried copying the scripts from BruControl and pasting them into Notepad. Then I deleted the scripts from BruControl, created new ones and copy & pasted from Notepad back into BruControl. I even tried deleting the scripts from BC and retyping them but neither of these resolved the issue.
Changing themes has the same results (I tried Office Black inside The Bezier as suggested, also Metropolis and Metropolis Dark).
I also just noticed that none of the variables will not allow a change in properties. I am able to toggle User Control on and off and select the script in the drop down menu but when I close the variables properties, then reopen the variable's property window, the changes were not saved and there is no script associated with the variable. This happens with all the variables in all the work spaces and configurations.
I spoke too soon; I'm still having the same problem with the script(s) not loading properly in the script window after changing between different configurations. This is happening on both ver 1.0 and the beta ver 1.1. I even switched my BC license to a newer, dedicated brewing PC thinking that running BC on a virtual machine on a Mac PowerBook may be causing the issue but the problem still exists on the PC. There is not much running on the PC since it has a clean install of Windows 10.
I have two different configurations with only a single script written for each configuration. Both are relatively short scripts setup for testing this issue. When I switch from one configuration to the other (and back again), the script area comes up blank and the user controls (run, resume, step, load, reset...) are dimmed out but the script is definitely running since all the screen controls and variables still respond to the script. I have found that by adding a second (blank) script (i.e. "Script 1") I can click on the blank script, then click back on the original script, the script areas does a refresh and the original script becomes visible again.