Closed Erquint closed 1 month ago
Using the 4af2d59 commit as a template betrayed me in the localization strings department, heh.
Well, it was a trivial fix — the entries already existed for this. Just needed to reference them without creating duplicates.
All checks passed. Kept it a draft PR in accordance with your rules.
DO NOT submit a PR unless it the connected issue is marked as ready to build or approved indirectly by an org member. This enables us to have a discussion on the idea before anyone invests time on the implementation.
— https://github.com/files-community/Files/blob/main/.github/CONTRIBUTING.md
Once the issue is marked as ready for PR, I'll make it a PR ready for review.
Thanks for the suggestion. And as for…
However, note that this may be rejected after all because the linked issue is still marked as planning.
That's why I'm keeping it a draft. 💁♂️
I think you misunderstood.
- Press [Ctrl]+[Alt]+[S] as the default keybinding for ToggleSidebar.
- Observe the sidebar and note if it has either collapsed or expanded.
I've tried these steps, and it doesn't look like anything changes.
I'll see if I can build in CLI…
Not installing MVS under any circumstances.
Is there a way to make portable builds for rapid iteration without reinstallation?
Wait, you didn't even test the changes 😬
And as for portable builds, you can download the AppxPackages
archive generated from the CI pipeline.
I left the PR a draft, remember?
And included testing steps.
It's a collaborative project.
I did try the workflow artifact build under a sandbox but wasn't able to have it install.
Didn't want it to mess with my existing installation, but I guess I'm gonna get rid of Files anyway, so I'll replace it with a development/test build.
But waiting on GH actions to build the binaries might not make very rapid iteration of local development.
Installing versions of Files from different production channels would not affect other channels.
Didn't want it to mess with my existing installation, but I guess I'm gonna get rid of Files anyway, so I'll replace it with a development/test build.
The dev builds have a different package name so you can have both versions installed at the same time.
I left the PR a draft, remember? And included testing steps. It's a collaborative project.
No harm done, don't worry about it 🙂
Installed the artifact with Visual Studio 2022 Developer PowerShell v17.11.5
bundled with MSBuildTools.
Normal PowerShell 7.4.6
couldn't install it, because M$ broke AppX in it.
Tested the action — it doesn't work.
Thinking if SidebarResizer_DoubleTapped
can be helpful here.
https://github.com/files-community/Files/blob/39df64d692a83f01eb69dab96dc261a3d0bc9976/src/Files.App/UserControls/Sidebar/SidebarView.xaml.cs#L193-L205
https://github.com/files-community/Files/blob/39df64d692a83f01eb69dab96dc261a3d0bc9976/src/Files.App/UserControls/Sidebar/SidebarView.xaml#L109
Erm, no. I did something stupid. Need to refer to the instance…
Just spotted the typo — wasn't using the interface.
Wait, wasn't there an interface..? 🤔 I need rest… Oh, it's the second instance of the same.
Yeah, I'm definitely doing this wrong.
Error: D:\a\Files\Files\src\Files.App\Actions\Show\ToggleSidebarAction.cs(9,20): error CS0246: The type or namespace name 'ISidebarViewModel' could not be found (are you missing a using directive or an assembly reference?) [D:\a\Files\Files\src\Files.App\Files.App.csproj]
Maybe I need to expand the interface… Erm, the type isn't found… Namespace scope..?
Please advise.
😂
@0x5bfa Well, that doesn't look like advice to me.
Why wouldn't you like to install Visual Studio? I'm sure using it would make this easier.
Lets try to stay on topic
Aight, let's try that.
ISidebarViewModel
is still out of scope, so it's the same issue still.
Added a
ToggleSidebar
action, imitating 4af2d59 as a template.Resolved / Related Issues
Steps used to test these changes
[Ctrl]+[Alt]+[S]
as the default keybinding for ToggleSidebar.[Ctrl]+[Shift]+[P]
).Not quite seeing how I could test this myself yet. Assuming that having imitated an equivalent commit closely should make this a relatively straightforward contribution nevertheless.
As for the callback contents, it seemed like there's three ways of doing this — through:
SidebarResizer_DoubleTapped
. Was my initial plan.SidebarDisplayMode.Expanded
/SidebarDisplayMode.Compact
. Seemed abstracted away.AppearanceSettingsService.IsSidebarOpen
. Gone with this one.Used the latter for this PR to closely match the reference commit.