An open source model would be more daunting but could work out better. You are working pretty close with users files op. No third-party code review like what would be possible if the code was on GitHub etc.
I don't know much about signing things myself, would you have a link to some resources that you'd recommend? And I'm not sure, but doesn't the windows store only deal with UWP applications? If so this program wouldn't be feasible there. Which I'm grateful for as I have it set up myself. But if it makes you uncomfortable to test, in a few weeks it will be on the Store and more stable version, and this is just a change for people to test early, and for me to get crash reports to fix the bugs faster.ġ00% agree, extremely simple to do these days. You can also test it in Windows Sandbox if you have any Windows other than Home. If crash message is in Russian, I will know that much. On crash program sends stack trace, the same things that any Store app collects, but doesn't tell me anything about the user.
I'll update it, but in short, it downloads 9 byte file on each window open with current version number to compare it with current version, and the ClickOnce version also downloads the manifest. This is the same privacy text that is linked from the Microsoft Store but if you have concerns, please let me know and I can clarify in the same text for anyone else that might have the same concerns. The v2 is on the store certified with MS Store certificate, and in a few weeks I will replace it with v3. No thumbnail grid support yet (it does support thumbnails in a list view which you can see in screenshot grid view is planned) There is no undo for file operations as Windows doesn’t expose APIs for that You cannot browse content of zip files but extraction is supported (or use 7zip or other archivers you have through context menu) MTP devices (phones) are not supported due to buggy protocol that can lead to data loss OC uses Windows copy/move/delete operations so those are the default Windows progress dialogs, and unfortunately can't be in colored in a theme color but those operations are as fast and as reliable as using File Explorer.
Context menu doesn’t support extensions that draw pictures or other non-standard elements, so if it crashes on right-click you will need to disable that extension. OC uses Windows default shell context menu and can only call it, so it is not in theme color (custom context menu will be considered in the future). No Windows S or ARM processor support (not planned) Insider build 21327 is NOT supported (Acrylic window effect rendering causes extreme system slowdown)
0 kommentar(er)
