build 1970 - new UI, part IV
Re: build 1970 - new UI, part IV
Another issue - color theme malfunctions.
I suspect it might be related to using a custom font.
I suspect it might be related to using a custom font.
-
- Posts: 102
- Joined: Tue Jun 28, 2016 6:17 pm
- Location: NN, Russia
Re: build 1970 - new UI, part IV
when editing hotkeys in preferences: overlapped hotkeys are not checked for collision
also - suggestion - add search by name or key to this list
also - suggestion - add search by name or key to this list
Last edited by d0ublezer0 on Sat Jan 28, 2017 5:18 pm, edited 1 time in total.
-
- Posts: 102
- Joined: Tue Jun 28, 2016 6:17 pm
- Location: NN, Russia
Re: build 1970 - new UI, part IV
Copy in place dialog localisation:
![Image](http://image.prntscr.com/image/2248077500494b8b8a30b11f95ae4d1d.png)
![Image](http://image.prntscr.com/image/2248077500494b8b8a30b11f95ae4d1d.png)
-
- Posts: 102
- Joined: Tue Jun 28, 2016 6:17 pm
- Location: NN, Russia
Re: build 1970 - new UI, part IV
FTP reload location Cmd+R not affects
Re: build 1970 - new UI, part IV
I'll add an option to hide it manually, like in terminal's settings.
BTW, scrollbar should be displayed only when actual scrolling happens, is it much of a problem?
Confirming, will fix it.
UPDATE: fixed.
Huh, I don't think it's possible without some tricks, since their layout is pretty different - one has button on left side and another has it on right side.
Confirming, have fixed it.
This is interesting, how can I reproduce this issue?
Agree, I want this feature too, but definitely not in this version.d0ublezer0 wrote: ↑Sat Jan 28, 2017 4:59 pmwhen editing hotkeys in preferences: overlapped hotkeys are not checked for collision
also - suggestion - add search by name or key to this list
Well.. it's a complicated story.
NC does some aggressive caching when dealing with FTP servers, otherwise it would be quite painful to work with them (tnx to silliness of this protocol).
Cmd+R currently reloads contents of a current panel and does nothing with internal state of VFS.
It's possible to change this logic a bit and add a discrete command for "refreshing" (i.e. discarding caches) a VFS state regarding some path.
Does it irritate you much?
Re: build 1970 - new UI, part IV
Short question: what's the purpose of reloading the current panel if not to trigger a refresh of the underlying VFS?Cmd+R currently reloads contents of a current panel and does nothing with internal state of VFS.
Re: build 1970 - new UI, part IV
Well, I've checked what's going on there, and it turns out to be much trickier to completely hide these scrollbars without ruining the scrolling functionality itself. Looks like this would require some hacking, which I prefer to avoid.
Lets clarify this issue, is that a scrollbar that always stays on screen or is that a scrollbar that appears only when actual scrolling happens?
Even with external PC-style mouses its possible to hide scrollbars while there are not used:
build 1974: one crash
Crashed while navigating, see attached crash report.
-
- Posts: 102
- Joined: Tue Jun 28, 2016 6:17 pm
- Location: NN, Russia
Re: build 1970 - new UI, part IV
mike,
it absolutely does not irritate me.
it does not allow me to work normally))
I often upload files to the server, and then verifies them in the GUI.
if I already deleted the files from the administrative panel, I do not see any changes on the server, and do not understand the real state.
by the way, total commander has ability to reload current location
it absolutely does not irritate me.
it does not allow me to work normally))
I often upload files to the server, and then verifies them in the GUI.
if I already deleted the files from the administrative panel, I do not see any changes on the server, and do not understand the real state.
by the way, total commander has ability to reload current location
-
- Posts: 102
- Joined: Tue Jun 28, 2016 6:17 pm
- Location: NN, Russia
Re: build 1970 - new UI, part IV
QuickView (by space)":
![Image](http://image.prntscr.com/image/c4d8ba98ea03491c828e9a0273f13174.png)
I think this is because the associated application may not use the quick view.
plain text files are viewed normally.
![Image](http://image.prntscr.com/image/c4d8ba98ea03491c828e9a0273f13174.png)
I think this is because the associated application may not use the quick view.
plain text files are viewed normally.