vList containers (file or member) can store Lingo variables that contain the media of a member. This can be very useful for example in a situation where you plan to update a Director project at runtime using the internet or a CD-ROM. You can do so by preparing your movie with placeholder members of the same type as those you plan to distribute in the future. At runtime you retrieve the new member media from a vList storage file and replace the movie's member media with the new media. The movie acts as a content shell so that only the changed media must be retrieved, which is more efficient.

vList members are normal Director members, so you can also store their media in a Lingo variable or store it in another vList container. In fact you can even store the media of a vList member inside itself, but you should be advised that what you store in that case is the previous state of that member:

memList = new (#vlist)

put 1 into member memList

memList.content = memList.media -- storing member().media into itself

memList.media = memList.content -- restoring to the previous state

put memList.content

-- 1