Update on UWP File explorer! Exciting stuff first!

Reveal style was applied to the home page grid (That thing in WinX where the borders change color in proximity to the mouse)

Clickable buttons in the title bar! This is the first step to tabs!

Converted a lot of things that were generated dynamically in C# to UserControls in XAML, for easier reading and even improved code-behind options.

Pulled my hair out getting rid of System.IO - System.IO is not made for UWP and stops working in certain situations. Now using Windows.Storage, which is a lot more async. I have gotten much friendlier with the dispatcher.

Pain from the operation is really fading and school doesn't start for a couple days, so I hope to get a beta out before school starts, and more realistically, get the tab system done before school starts.

I just wanted to create a small website using PHP MVC... Haha

Well here it goes,

I started out in customer support (A lot of stuff to tell here).

1.
One of my colleagues would come to work drunk, like every day he would smell of boze (the hard stuff 80%+). When a customer got on his nerves he endet the call and threw his Keyboard across the room. He worked in the company 3+ Years after I left.

2. Another colleague would connect to his Personal Computer at his home and play WoW while at work ( Allthough the man was a genius with a lot of free time, until a new task was assigned to him)

3. My Boss at the time did some really shitty things. I worked 17 hour days (while I was 18) for a week, and at the end of the week he shredded the accrued overtime with some Bullshit Explanation. (I did not stay long after this shitshow happened).

4. A dispatcher who sent our technicians out scheduled their tasks so that they were on the road for weeks and did not see their families. This led to a very strong turnover among technicians.

And yes, this company still operates today.

anyone having a good understanding of kotlin coroutines? the weird extension lambdas, coroutine scopes, context , dispatcher and suspend are not making much sense to me. i can post a longer query, but first i just need to understand the relationship between a scope, context and dispatcher?

Wasted over two hours today on a stupid bug: for some reason, every event was handled two times on my local machine.

Why? Because although all services are readonly after instantiation, the EventDispatcher isn't: it is modified when registering event handlers. Meaning the very same instance of the actual EventSubscriber was reused for the async- and sync event dispatcher. Which are just simple wrappers for primary and secondary use cases, but use the _same_ instance of the actual EventSubscriber in my dev-environment as I now know.

Thankfully a shallow clone did the trick. Of course it would be possible to simply create a new instance, but this is one of the few services which are autoconfigured by the framework.

Don't know what to make of this to be honest. "Play stupid games, win stupid prizes!" I guess...