> Using a map for this purpose would fit exactly. If you > need also the reverse translation then it might not be the best fit > anymore
There are reverse translations. The problem is that *both* names have to be checked because EmbeddedFiles does not know in advance which name will be checked. > I would design the interface in such a way that it is always clear which > name has to be used. IMO there are three types of names: > > - always embedded > - always external > - depending on the embedded status of that inset, either external or > embedded. This is the case now. > I would prefer to have each file only once. It does not make sense to me to > allow to embed a file for one inset, but then say in another inset that > also uses the same file to not embed it. That is a contradiction that > should not exist IMO. This is the case now. Multiple insets can be related to the same file; and if the embedding status of a file is changed, all insets are affected. Cheers, Bo
