To my surprise, I discovered the GUI action folder is still executed even if we're in console mode and vice versa. The GUI panels are just skipped over, but other actions like "Set IA variables" were being run. That was really screwing me up!
I put a rule on each folder to check $INSTALL_UI$. If its SWING, GUI folder will run. If its not SWING the Console folder will run.
Just want to know if that was the best way to handle it or is there another way?
I guess this is by design: i.e. Set IA variables is an action that does not depend on the graphical mode, so it'll always execute; heck, it will execute even in silent mode, if you have it (in this case both panels and consoles are skipped); so if you need actions done differently depending on the installation mode, indeed the best idea would be to test it right from the beginning and to have rules depending on the mode.
