Opened 13 years ago
#736 new annoyingness
blocking problem
| Reported by: | kjdon | Owned by: | nobody |
|---|---|---|---|
| Priority: | moderate | Milestone: | Collection building wishlist |
| Component: | Collection Building: Plugins | Severity: | minor |
| Keywords: | Cc: |
Description
Problem with current block_exp vs smart block mechanism.
For ISIS files, I would like to process the mst file, then block the corresponding fdt and xrf files. I don't want to just use block_exp for fdt and xrf, as if these don't have a corresponding mst then it would be nice to warn the user.
Using the store_block_files routine, and empty block_exp works fine on command line. However, not for GLI.
- it complains when you drag in fdt and xrf that no plugin can process the files.
So, add these two to the process exp instead. Then all three get highlighted as explodable. and the plugin needs to be fixed up so it doesn't try to process the fdt and xrf.
can we do anything better? I have left block_exp in for now.
Note:
See TracTickets
for help on using tickets.
