|
From: Roman T. <tso...@gm...> - 2017-10-28 18:11:43
|
Hi everybody, There is a feature request I would +1, columns customization. But now it is not possible due to the nature of the table of files/items. And this is why (for those who is not aware including me): The browser uses virtual file system layer to deal with files/items and supports a number of those: "filefs" "urlfs" "roots" "favourites" at least. The grid does not distinguish between them but mixes altogether on demand. On every openning of a directory a particular vfs is given and table model asks that fs for attriutes the fs supports. Every attribute becomes a column in the table (like type, size, last modified). Those attributes (columns) are not replaced but new ones added to existing list. So we can not have a defined column set for every fs, but the resulting list is unpredictable by nature. This mechanism makes possible a nice facility you can see if you have any items in your favourites. Add directory to favourites, open favourites (favourites fs is loaded, which has two columns), click on the plus sign to expand that dir and what happens is that a new fs queried and its attributes added as columns to existing ones. I wonder is this feature actually used/necessary? Would it be better prevent FSs from mixing and have separated column sets? (In case of favourites it could just add new items to the list so expansion still possible but not adding new columns) -- Best regards, Roman. mailto: tso...@gm... |