Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code Quality: Introduced IWindowsAppLauncherService #15927

Closed

Conversation

0x5bfa
Copy link
Member

@0x5bfa 0x5bfa commented Aug 3, 2024

Resolved / Related Issues

This also involves with IShellItem, methods of which return HRESULT but CsWin32 generates those methods with void returned. But this issue can be detoured by not allowing marshaling by CsWin32. However, this is blocked by WinUIEx because of CsWin32 issue, conflicting generated code modifiers between internal (WinUIEx) and public (Files). WinUIEx removal is almost done so this should be able to be continued soon again.

Steps used to test these changes

None yet

@0x5bfa 0x5bfa force-pushed the 5bfa/CQ-IWindowsLaunchService branch from ac71456 to 42a305b Compare August 3, 2024 03:00
@0x5bfa 0x5bfa changed the title Code Quality: Introduced IWindowsLaunchAppService Code Quality: Introduced IWindowsAppLauncherService Aug 3, 2024
@yaira2 yaira2 self-requested a review August 4, 2024 14:42
@0x5bfa
Copy link
Member Author

0x5bfa commented Aug 4, 2024

I have CreateFile method using Vanara in this file yet as well.
Imo, I'd like to replace them after this to reduce the work of review because I already made complicated changes.
What do you think?


Also, merging this after v3.6 looks good to me.

Copy link
Member

@yaira2 yaira2 Aug 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please add some comments? I understand this is based on existing code, but our standard practice is to include comments when creating an interface. Thanks!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I forgot that even though I appended inheritdoc to implementations lol

@@ -52,7 +53,7 @@ private async void GoToStorageSense_Click(object sender, RoutedEventArgs e)
button.Tag.ToString() is not string path)
return;

await StorageSenseHelper.OpenStorageSenseAsync(path);
await WindowsLaunchAppService.LaunchStorageSensePolicySettingsAsync();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should you include the path in the arguments?

Copy link
Member Author

@0x5bfa 0x5bfa Aug 5, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The first implementation to include path is made by Gave (3 yrs ago) but I'm not sure why because Storage Sense works for only system drive and for the whole system drive not for specifically a path.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually path isn't used to be passed to settings to give extra context.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a thread on GitHub about this with more details, but in any event, it makes a difference for which page is opened in Settings.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both open wrong page.

For other than C (system) drive:
image

For thers:
image

Both should open:
image

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My implementapention opens what should be opened.

Copy link
Member

@yaira2 yaira2 Aug 5, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both open wrong page.

It's supposed to open the Storage Page for the C:\ drive, and the "Storage used on other drives" page for other drives.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even so, how would you free up storage for other drives? The "Storage used on other drives" doesn't contains any free up page.
As to C, why not open Policy page directly.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume this weird page navigation might come from win10 when Gave implemented

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even so, how would you free up storage for other drives? The "Storage used on other drives" doesn't contains any free up page.

You can access the "Free up storage" page by clicking on a drive. Ideally we'd open directly to that page, but that's not supported by the Settings app.

@0x5bfa
Copy link
Member Author

0x5bfa commented Sep 8, 2024

This should not be DI'd.
Ill create a new one for this.

@0x5bfa 0x5bfa closed this Sep 8, 2024
@0x5bfa 0x5bfa deleted the 5bfa/CQ-IWindowsLaunchService branch October 5, 2024 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants