Thanks for clarifying this image list vs image selection thing. I think it’s extremely confusing as currently implemented. I would recommend you simplify things so that it works like this:
All image import happens through the same “import images”. If you select an image, that image comes in. If you select a folder, the contents of that folder (and children, depending on checkbox) comes in. If you select a .imagelist file, the contents of that list comes in. No matter how you imported stuff, the new files and duplicates found should be selected, and the console should say how many files were skipped duplicates and how many were actually imported.
You might add checkboxes for the “select after import” behavior – select duplicates, select added. You could have another checkbox which controls whether the actual image import happens or is just skipped, so that you could do the what the “import imagelist” currently does.
If you keep “import imagelist” as it is now – just a selection tool, then it absolutely should be moved from Workflow/Import to Alignment/Selection. Then it might make some sense.
As for registration vs component, it still sounds to me as if you are using two different words for the same thing, making it unnecessarily confusing for the user. The only difference is that you export a wider variety of (component / registration) formats than you import.
It’s also weird that you have Export “Images list” and then you also have “Image list” as a filetype for Export/Registration. I know the presence of an “s” can be very important in RC but I guess it doesn’t make a difference in this case?