Working with Subdirectories

Does anyone know if there’s an easy way to move a set of liquid classes to a new subdirectory? Right now, I have to save each liquid class individually to the new subdirectory, but it forces me to rename the file because it only works as a “save-as” option. There doesn’t seem to be a way to move the files without saving a duplicate.

I wish I could just drag and drop these files around as I see fit.

Fluent Control doesn’t let you drag & drop items to subdirectories. Your only options are to “Save As” the template to the new directory or you can edit the .lc file directly to change it I believe.

In my experience, the directory structure for LC’s is really for human eyes only. Fluent Control doesn’t do a great job of differentiating between something in subdirectory A versus something in subdirectory B or something in Local.

And so if you’re doing something like

Local/LiquidClass_A
Dev/LiquidClass_A
Prod/LiquidClass_A

FC is going to use the first one that it encounters when it goes to call it. It may never touch your Prod if it’s hitting Local and Dev first. Just give them different names and don’t rely on the directory structure too much for LC’s except as a tool to make it easier for humans to follow.

Maybe this changed in more recent versions of FC but hasn’t been my experience in 3.4 and earlier.

1 Like

Bummer - thanks for the snappy reply! Yeah, we have multiple users on our instrument and our liquid class section is starting to get really long and messy. It would be nice to better organize these liquid classes into folders.

Totally understand, I use subdirectories all of the time but I’ve realized that they’re not super functional for the Tecan and more for helping up (the users) organize our mess.

My other advice is to include a version number in the name so you can do something like

Local/LiquidClass_A_v0_00
Dev/LiquidClass_A_v1_10
Prod/LiquidClass_A_v1_00

1 Like