Recent Posts

Pages: [1] 2 3 4 5 ... 10
1
Okay, thank you, I will test it and report back when the change will be available in MultiUpdate.
2
Think I found issue. Should report correct error now in all situation.

Temp copy to local is coming.. ( I need for some other situations too. but it will not come in the next release.. maybe next after..)
3
Support and Feedback / Re: Proper column sizing in List view
« Last post by Mathias (Author) on January 20, 2025, 09:15:44 »
Quote
There are changes planed in the future for the list view. But not so that filename column is totally automatic.  I prefer to have the filename width be changable.  If I got 200 files.  190 of them are around 15 char.  but 10 of them have long 80char. Then I get a width that is WAY to long for most files.

If I understand correctly, you want to make an implementation where each column in List mode is as wide as its longest file name. That would result in columns that are not all of the same width. I don't know how would that look, aesthetically. Also at different events, like window resize for example, or creation of new objects, everything would have to be recalculated. If there are many files, it might be slow.
Ehh What.. Noo, I'm not talking abourt future stuff.  Im taking about why I do not want the auto size filename column that can't be changes like in TC, Currently in MC you can resize the filename width your self, And change that to work like TC. I think that would work worse instead of better



Quote
I don't do changes in MC based on what TC does, MC is not trying to be a clone of TC.  they are similar in many things. but I don't base features in MC on what TC do. If MC would be a clone of TC then there would be no point spending time developing MC.
MC does not have to be a clone of TC. I did not imply that. But it is hard to ignore the fact that TC is very widely used and can stand as a reference. To clone, as you say, means to copy everything. On the other hand, what I was saying in my post was to observe what others have done right. And TC has done a lot of them right. All those TC users are more likely to find a comfortable home in MC if they find familiar things. It is common sense to think that most people want to reuse what they already know and then learn a little extra, than to learn everything from the ground up when they change a software.
In a world where long file names, modification date and time are very important, you cannot have a List mode that leaves the user without seeing any of them properly.
Yes TC is used by many. MC is not. TC is commercial product, and must try to catch as many users as possible. I don't care about how many users I have. I developed MC mainly for my own needs, I don't make any money on MC. I have a day job.
MC is developed on my spare time, so I have to priorities what to spend time on. :)
I just get annoyed when people compare mc with other products. specially commercial.. The biggest reason MC is missing something is because I have not needed it. :)
But I do add stuff I never use my self. I got a long list of things to add and many of them are things I will never use my self. But it is more fun to add stuff I use my self. So things I use my self are higher priorities.
4
Support and Feedback / Re: Proper column sizing in List view
« Last post by ags on January 20, 2025, 08:43:53 »
Quote
There are changes planed in the future for the list view. But not so that filename column is totally automatic.  I prefer to have the filename width be changable.  If I got 200 files.  190 of them are around 15 char.  but 10 of them have long 80char. Then I get a width that is WAY to long for most files.

If I understand correctly, you want to make an implementation where each column in List mode is as wide as its longest file name. That would result in columns that are not all of the same width. I don't know how would that look, aesthetically. Also at different events, like window resize for example, or creation of new objects, everything would have to be recalculated. If there are many files, it might be slow.


Quote
I don't do changes in MC based on what TC does, MC is not trying to be a clone of TC.  they are similar in many things. but I don't base features in MC on what TC do. If MC would be a clone of TC then there would be no point spending time developing MC.

MC does not have to be a clone of TC. I did not imply that. But it is hard to ignore the fact that TC is very widely used and can stand as a reference. To clone, as you say, means to copy everything. On the other hand, what I was saying in my post was to observe what others have done right. And TC has done a lot of them right. All those TC users are more likely to find a comfortable home in MC if they find familiar things. It is common sense to think that most people want to reuse what they already know and then learn a little extra, than to learn everything from the ground up when they change a software.
In a world where long file names, modification date and time are very important, you cannot have a List mode that leaves the user without seeing any of them properly.
5
Ok, thanks. It's good to know it is on your todo list.
6
Support and Feedback / Re: Column autosizing in List view
« Last post by Mathias (Author) on January 20, 2025, 07:56:06 »
So in List mode it is important to:
- calculate the proper column width, so the size of the columns would be equal to the size of the longest name in the list, plus its extension;
- ignore the header (the one with Name, Ext, Size, Date). In List mode the header is there only for sorting, not for width;
- show the most important properties of the file to the user. Since the size, the date and the time of the file are not shown in columns in the panel, thay have to be shown somewhere: under the table. Otherwise you leave the user to fly blind.

List mode exists to allow the user to navigate easily through files. Notably, to be able to use the left_arrow and right_arrow, keys that do not work in Details mode.

Please see the screenshots attached. I highlighted the most important parts in colors red, green, blue.

TC ignores the header (red) and calculates the column width after the longest name+ext (green) and shows useful properties of the selected object (blue). The result? The user can easily see the full length of the names, and also under the table there is the size, date and time of the selected file. All is good. All the other orthodox file managers do this.

MC makes the header (red) and the column (green) equal in width. This makes no sense, it defeats the whole purpose of List mode. The result? The user cannot see all the long names because thay are truncated, and has no simple way of seeing the size, date and time of the object under the cursor at a glance, because under the table MC shows statistics of the selected files, less important info. :-\
[/quote]

There are changes planed in the future for the list view. But not so that filename column is totally automatic.  I prefer to have the filename width be changable.  If I got 200 files.  190 of them are around 15 char.  but 10 of them have long 80char. Then I get a width that is WAY to long for most files.

I don't do changes in MC based on what TC does, MC is not trying to be a clone of TC.  they are similar in many things. but I don't base features in MC on what TC do. If MC would be a clone of TC then there would be no point spending time developing MC.

7
That I can't reproduce. I can only reproduce it using Drag and drop.
Might be fixed so dialog is shown. Fixing to uncompress to temp in the future some day. That is directly a quick fix. It require a lot of work and I got other thing in the pipe before that. and Time I get to work on MC is also limited.
8
I am making another attempt here to clarify things. And bring objective proof to sustain my bug report.
In the video, in the left I have the phone, in the right I have the archive.
I am making 4 attempts to copy one file from the archive to the phone.
The first 2 are started by key F5. The last 2 are by dragging.
As you can see, from the user's perspective they are absolutely identical, because they produce identical results. One of them being that MC does not show the dialog saying it not possible to do that copy. And the other being that the operation fails.
Now, it would be much preferable to fix this by uncompressing into %temp% and copy from there to phone.
I mean much preferable to just showing a dialog that it is not possible. :D
https://streamable.com/1cjyj6
9
Using F5 it shows the dialog.. Drag and drop do not show it because it gets in using another way..

10
Support and Feedback / Re: Column autosizing in List view
« Last post by ags on January 19, 2025, 17:51:49 »
Please, please consider improving the List mode in MC. Because now it is there but it is not useful at all.

So in List mode it is important to:
- calculate the proper column width, so the size of the columns would be equal to the size of the longest name in the list, plus its extension;
- ignore the header (the one with Name, Ext, Size, Date). In List mode the header is there only for sorting, not for width;
- show the most important properties of the file to the user. Since the size, the date and the time of the file are not shown in columns in the panel, thay have to be shown somewhere: under the table. Otherwise you leave the user to fly blind.

List mode exists to allow the user to navigate easily through files. Notably, to be able to use the left_arrow and right_arrow, keys that do not work in Details mode.

Please see the screenshots attached. I highlighted the most important parts in colors red, green, blue.

TC ignores the header (red) and calculates the column width after the longest name+ext (green) and shows useful properties of the selected object (blue). The result? The user can easily see the full length of the names, and also under the table there is the size, date and time of the selected file. All is good. All the other orthodox file managers do this.

MC makes the header (red) and the column (green) equal in width. This makes no sense, it defeats the whole purpose of List mode. The result? The user cannot see all the long names because thay are truncated, and has no simple way of seeing the size, date and time of the object under the cursor at a glance, because under the table MC shows statistics of the selected files, less important info. :-\
Pages: [1] 2 3 4 5 ... 10