Small update on my UWP File Explorer:

Got some nice work done on the Navigation Box. A right click (Or long tap on touch displays) gives a context menu with subfolders, as opposed to the Classic application which had a drop-down button (This is not as friendly for touch, in my opinion)

A left click navigates to that folder.

Been a bit sick from my surgery, so not much progress these past few days, but I'm still happy with this.

Looks great! Now get some rest ;)

@Jilano It's only 3am. My wisdom teeth don't weigh me down anymore, without them, I'm a free man. I can stay up as long as I-

*Snore*

is always that checkbox beside every File there?

@lazyDev For now.

@AlgoRythm Can't wait to try it out.
Take care of your health.

Please also make the selection glow, it'll look nice

@AlgoRythm Hey man! Take care of your health.
Can we have a MacOS style file explorer thing where in it opens the folder towards the side while keeping the main directory to the left. More or less like target="_blank" thing. I don't know how to explain it better. 😂

📍

Ooh, looks so cool! Is there any forks that can be 'tested' on Win 7? ;)

I think the time it takes to show the list of files is a ~little~ long. Just saying

@melezorus34 Probably not, it uses the Win 10 SDK

@lazyDev I'm not sure if that's IO or XAML doing that, but I noticed that. If it's C# being shit, not much I can do about it. I don't have very many options in UWP, and I'm using "restricted capabilities" as it is!

@lazyDev @AlgoRythm in UWP, file system access happens through the runtime broker process associated with your UWP app instance. This is a pain in the ass because it slows down access to files on storage it also seems to be necessary as it checks the app's permission to access the files.

My music app takes about 7 seconds to get a flat list of all files in the music folder which has about 4500 tracks. The folder is indexed so it should be fast but I can see the runtime Brooker using up to 20% cpu and around 280MBs while the query is running. Couldn't find a way around this btw

@MrCSharp That makes me angry.

God help <c#>ers