toast notifications(+) #17

Merged
mshafer1 merged 41 commits from dev/toast_notifications_plus into master 2025-02-11 04:53:56 -05:00
7 changed files with 731 additions and 15 deletions
Showing only changes of commit 934edb79eb - Show all commits

View File

@@ -16,7 +16,7 @@ namespace ntfysh_client
private readonly NotificationListener _notificationListener;
private bool _startInTray;
private bool _trueExit;
private NotificationDialog notificationDialog;
private NotificationDialog _notificationDialog;
public MainForm(NotificationListener notificationListener, bool startInTray = false)
{
@@ -34,7 +34,7 @@ namespace ntfysh_client
LoadSettings();
LoadTopics();
this.notificationDialog = new NotificationDialog();
_notificationDialog = new NotificationDialog();
}
protected override void SetVisibleCore(bool value)
@@ -79,12 +79,12 @@ namespace ntfysh_client
}
else
{
this.notificationDialog.ShowNotification(
_notificationDialog.ShowNotification(
title: finalTitle,
message: e.Message,
timeout_ms: (int)TimeSpan.FromSeconds((double)Program.Settings.Timeout).TotalMilliseconds,
icon: priorityIcon,
showTimeOutBar: Program.Settings.CustomTrayNotificationsShowTimeoutBar
showTimeOutBar: Program.Settings.CustomTrayNotificationsShowTimeoutBar,
showInDarkMode: Program.Settings.CustomTrayNotificationsShowInDarkMode
);
}

View File

@@ -17,118 +17,118 @@ namespace ntfysh_client
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private const int ScreenMargin = 20;
private int _timeout = 0;
private System.Timers.Timer? displayTimeoutTimer = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private System.Windows.Forms.Timer? updateTimer = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private Stopwatch? shownStopwatch = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private System.Timers.Timer? _displayTimeoutTimer = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private System.Windows.Forms.Timer? _updateTimer = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private Stopwatch? _shownStopwatch = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private ToolTipIcon? _icon;
private int _progress_value = 0;
private int progress
{
get { return this._progress_value; }
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
get { return _progress_value; }
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
set
{
this._progress_value = value;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.progressBar1.Value = value;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_progress_value = value;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
progressBar1.Value = value;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
}
public bool IsVisible
{
get { return this.Visible; }
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
set { this.Visible = value; }
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
get { return Visible; }
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
set { Visible = value; }
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
public NotificationDialog()
{
this.ShowInTaskbar = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.IsVisible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.TopMost = true;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
ShowInTaskbar = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
IsVisible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:09:54 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:05 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
TopMost = true;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
InitializeComponent();
InitializeWindowHidden();
}
public void ShowNotification(string title, string message, int timeout_ms = -1, ToolTipIcon? icon = null, bool showTimeOutBar = true, bool showInDarkMode = true)
{
if (this.IsVisible)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (IsVisible)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
// close the current notification
this.handleTimeout(null, null);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
handleTimeout(null, null);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
// setup data
this._icon = icon;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (this._icon != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_icon = icon;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (_icon != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
this.iconBox.Image = ConvertToolTipIconToImage(_icon.Value);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
iconBox.Image = ConvertToolTipIconToImage(_icon.Value);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:11 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:16 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
this.tbTitle.Text = title;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.tbMessage.Text = message;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
tbTitle.Text = title;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
tbMessage.Text = message;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
// setup timers
if (this.displayTimeoutTimer != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (_displayTimeoutTimer != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:16 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:29 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
this.displayTimeoutTimer.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.displayTimeoutTimer.Dispose();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_displayTimeoutTimer.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_displayTimeoutTimer.Dispose();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
if (this.updateTimer != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (_updateTimer != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
this.updateTimer.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.updateTimer.Dispose();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_updateTimer.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_updateTimer.Dispose();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
if (timeout_ms > 0)
{
this.displayTimeoutTimer = new System.Timers.Timer(timeout_ms);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
displayTimeoutTimer.Elapsed += handleTimeout;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.displayTimeoutTimer.Start();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_displayTimeoutTimer = new System.Timers.Timer(timeout_ms);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_displayTimeoutTimer.Elapsed += handleTimeout;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_displayTimeoutTimer.Start();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (showTimeOutBar)
{
this.progress = 100;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.updateTimer = new System.Windows.Forms.Timer();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
updateTimer.Interval = 100;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.updateTimer.Tick += this.UpdateProgress;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.updateTimer.Start();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
progress = 100;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_updateTimer = new System.Windows.Forms.Timer();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_updateTimer.Interval = 100;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_updateTimer.Tick += UpdateProgress;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_updateTimer.Start();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.shownStopwatch = new Stopwatch();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.shownStopwatch.Start();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_shownStopwatch = new Stopwatch();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_shownStopwatch.Start();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.progressBar1.Visible = true;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.lbTimeout.Visible = true;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this._timeout = timeout_ms;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
progressBar1.Visible = true;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
lbTimeout.Visible = true;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_timeout = timeout_ms;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
} else
{
this.progressBar1.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.lbTimeout.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
progressBar1.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
lbTimeout.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
alexhorner commented 2025-01-11 05:00:52 -05:00 (Migrated from github.com)
Review

Nitpick: One liner & newline

SetWindowPosition();

if (playNotificationSound) PlayNotificationSound();
Nitpick: One liner & newline ```csharp SetWindowPosition(); if (playNotificationSound) PlayNotificationSound(); ```
mshafer1 commented 2025-01-11 09:58:06 -05:00 (Migrated from github.com)
Review

applied

applied
}
else
{
this.progressBar1.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.lbTimeout.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
progressBar1.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
lbTimeout.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
// ok, show the window
this.Show();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.SetWindowPosition();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
Show();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
SetWindowPosition();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
private void UpdateProgress(object? sender, EventArgs e)
{
if (this.shownStopwatch == null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (_shownStopwatch == null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
return;
}
this.progress = (int)((this._timeout - this.shownStopwatch.ElapsedMilliseconds) * 100 / this._timeout);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.lbTimeout.Text = $"{(int)(this._timeout - this.shownStopwatch.ElapsedMilliseconds) / 1000}";
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
progress = (int)((_timeout - _shownStopwatch.ElapsedMilliseconds) * 100 / _timeout);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
lbTimeout.Text = $"{(int)(_timeout - _shownStopwatch.ElapsedMilliseconds) / 1000}";
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
protected override void SetVisibleCore(bool value)
{
this.SetWindowPosition();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
SetWindowPosition();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (value)
{
this.BringToFront();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
BringToFront();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
AnimateWindow(
this.Handle,
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
Handle,
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
time: 250,
flags: NFWinUserAnimateWindowConstnats.AW_SLIDE | NFWinUserAnimateWindowConstnats.AW_VER_NEGATIVE
);
@@ -143,35 +143,35 @@ namespace ntfysh_client
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private void SetWindowPosition()
{
int workingtop = Screen.PrimaryScreen.WorkingArea.Height - this.Height;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.Top = workingtop - NotificationDialog.ScreenMargin;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
int workingtop = Screen.PrimaryScreen.WorkingArea.Height - Height;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
Top = workingtop - NotificationDialog.ScreenMargin;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
int workingleft = Screen.PrimaryScreen.WorkingArea.Width - this.Width;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.Left = workingleft - NotificationDialog.ScreenMargin;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
int workingleft = Screen.PrimaryScreen.WorkingArea.Width - Width;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
Left = workingleft - NotificationDialog.ScreenMargin;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
alexhorner commented 2024-12-21 05:59:04 -05:00 (Migrated from github.com)
Review

Nitpick: newlines

this.BringToFront();

AnimateWindow
(
    ...
);
Nitpick: newlines ```csharp this.BringToFront(); AnimateWindow ( ... ); ```
mshafer1 commented 2024-12-21 10:58:55 -05:00 (Migrated from github.com)
Review

Added

Added
private void ui_hide_window(object? sender, EventArgs? e)
{
AnimateWindow(
this.Handle,
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
Handle,
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:58:07 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:58:32 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
time: 250,
flags: NFWinUserAnimateWindowConstnats.AW_SLIDE | NFWinUserAnimateWindowConstnats.AW_VER_POSITIVE | NFWinUserAnimateWindowConstnats.AW_HIDE
);
this.IsVisible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
IsVisible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
private void handleTimeout(object? sender, EventArgs? e)
{
this.cancelTimer();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (this.InvokeRequired)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
cancelTimer();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (InvokeRequired)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
// on a background thread, so invoke on the UI thread
this.Invoke(new Action(() => this.ui_hide_window(sender, e)));
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
Invoke(new Action(() => ui_hide_window(sender, e)));
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
else
{
// in the UI thread, invoke directly
alexhorner commented 2024-12-21 05:59:54 -05:00 (Migrated from github.com)
Review

Nitpick: Newlines, same as earlier AnimateWindow example

Nitpick: Newlines, same as earlier `AnimateWindow` example
mshafer1 commented 2024-12-21 10:59:07 -05:00 (Migrated from github.com)
Review

added

added
this.ui_hide_window(sender, e);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
ui_hide_window(sender, e);
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
}
alexhorner commented 2024-12-21 05:59:59 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
mshafer1 commented 2024-12-21 10:59:37 -05:00 (Migrated from github.com)
Review

I added a blank line before the call to the parent class

I added a blank line before the call to the parent class
@@ -193,16 +193,16 @@ namespace ntfysh_client
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private void InitializeWindowHidden()
{
this.Opacity = 0;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.ShowNotification("Title", "Message");
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.IsVisible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.Opacity = 1;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
Opacity = 0;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
ShowNotification("Title", "Message");
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
IsVisible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
Opacity = 1;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
private void btnClose_Click(object sender, EventArgs e)
{
// immediate
this.IsVisible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
IsVisible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
private class NFWinUserAnimateWindowConstnats
@@ -220,43 +220,43 @@ namespace ntfysh_client
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
private void window_MouseDown(object sender, EventArgs e)
{
this.cancelTimer();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
cancelTimer();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
private void cancelTimer()
{
if (this.InvokeRequired)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (InvokeRequired)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
// on a background thread, so invoke on the UI thread
this.Invoke(new Action(() =>
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
Invoke(new Action(() =>
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
this.lbTimeout.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.progressBar1.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
lbTimeout.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
progressBar1.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}));
}
else
{
// in the UI thread, invoke directly
this.lbTimeout.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.progressBar1.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
lbTimeout.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
progressBar1.Visible = false;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
if (this.displayTimeoutTimer != null) // check if the timer has already been disposed
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (_displayTimeoutTimer != null) // check if the timer has already been disposed
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
this.displayTimeoutTimer.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.displayTimeoutTimer.Dispose();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.displayTimeoutTimer = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_displayTimeoutTimer.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_displayTimeoutTimer.Dispose();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_displayTimeoutTimer = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
if (this.updateTimer != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (_updateTimer != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
this.updateTimer.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.updateTimer.Dispose();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.updateTimer = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_updateTimer.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_updateTimer.Dispose();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_updateTimer = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
if (this.shownStopwatch != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
if (_shownStopwatch != null)
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
{
this.shownStopwatch.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
this.shownStopwatch = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_shownStopwatch.Stop();
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
_shownStopwatch = null;
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
}
}
}
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:02 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:38 -05:00 (Migrated from github.com)
Review

Nitpick: One liner? if (this.shownStopwatch is null) return;

Nitpick: One liner? `if (this.shownStopwatch is null) return;`
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:57:57 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 05:59:25 -05:00 (Migrated from github.com)
Review

What's the purpose of this override?

What's the purpose of this override?
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:00:03 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:02:43 -05:00 (Migrated from github.com)
Review

This is a great candidate for the new switch expression syntax, and then it can be turned into a lambda

private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch
{
    ToolTipIcon.Info => SystemIcons.Information.ToBitmap(),
    ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(),
    ToolTipIcon.Error => SystemIcons.Error.ToBitmap(),
    _ => null
}
This is a great candidate for the new `switch expression` syntax, and then it can be turned into a lambda ```csharp private Image? ConvertToolTipIconToImage(ToolTipIcon icon) => icon switch { ToolTipIcon.Info => SystemIcons.Information.ToBitmap(), ToolTipIcon.Warning => SystemIcons.Warning.ToBitmap(), ToolTipIcon.Error => SystemIcons.Error.ToBitmap(), _ => null } ```
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:03:45 -05:00 (Migrated from github.com)
Review

Nitpick: Lambda one liner

Nitpick: Lambda one liner
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:35 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:05:39 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter title casing without underscores

Nitpick: Naming convention is capitalised first letter title casing without underscores
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:06:34 -05:00 (Migrated from github.com)
Review

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section

Nitpick: convention is use of _ for private variables to avoid the use of this. Goes for all others in this section
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:17 -05:00 (Migrated from github.com)
Review

This appears to be set but never read outside of the progress getter

This appears to be set but never read outside of the `progress` getter
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:08:39 -05:00 (Migrated from github.com)
Review

Could this just read this.progressBar1.Value instead?

Could this just read `this.progressBar1.Value` instead?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:01 -05:00 (Migrated from github.com)
Review

Any reason we're wrapping this? Is it protected usually?

Any reason we're wrapping this? Is it protected usually?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:09:43 -05:00 (Migrated from github.com)
Review

Does this need thises?

Does this need `this`es?
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:00 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:06 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:10:24 -05:00 (Migrated from github.com)
Review

Nitpick: newline

Nitpick: newline
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:11:04 -05:00 (Migrated from github.com)
Review

Nitpick: Naming convention is capitalised first letter

Nitpick: Naming convention is capitalised first letter
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:14:19 -05:00 (Migrated from github.com)
Review

Nitpick: timeout_ms should be timeoutMilliseconds

Nitpick: `timeout_ms` should be `timeoutMilliseconds`
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:07 -05:00 (Migrated from github.com)
Review

immediate?

immediate?
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
alexhorner commented 2024-12-21 06:16:43 -05:00 (Migrated from github.com)
Review

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.

I try to rename my elements to match the TitleCase naming convention. Not a major one, just a nice-to-have. I appreciate this isn't consistent within the application anyway.
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 08:42:00 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:07:45 -05:00 (Migrated from github.com)
Review

I'll change the comment to better explain the desired intent

            // don't animate, immediately "close"

rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).

I'll change the comment to better explain the desired intent ```suggestion // don't animate, immediately "close" ``` rationale: if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of this, I intentionally implemented the button close handler to immediately close the pop up (don't animate, and don't wait for the timeout).
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 09:10:55 -05:00 (Migrated from github.com)
Review

I think this is just left over from my first attempts at getting the animation to work.

I think this is just left over from my first attempts at getting the animation to work.
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:42 -05:00 (Migrated from github.com)
Review

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).

I went through and attempted to add a blank line before every if statement that was not the opening statement of the parent scope (and if preceded by a comment, the blank line went before the comment).
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:57:52 -05:00 (Migrated from github.com)
Review

changed

changed
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:58:24 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 10:59:02 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:02 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:11 -05:00 (Migrated from github.com)
Review

updated

updated
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:00:17 -05:00 (Migrated from github.com)
Review

swapped

swapped
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:37 -05:00 (Migrated from github.com)
Review

removed

removed
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:04:52 -05:00 (Migrated from github.com)
Review

yes, I originally thought there would be more to the setter. Removed.

yes, I originally thought there would be more to the setter. Removed.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:05:59 -05:00 (Migrated from github.com)
Review

Not in the end. Removed. (I had originally though the UI would be .SetInfo(...); .Show() or something, but the way it is now has a better expandability and doesn't use this.

Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:22 -05:00 (Migrated from github.com)
Review

no, that's just what style I was used to back when I last worked in C# (removed all)

no, that's just what style I was used to back when I last worked in C# (removed all)
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:06:56 -05:00 (Migrated from github.com)
Review

This got changed to timeoutSeconds to deal with corresponding comment in MainForm.cs

This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:20 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:23 -05:00 (Migrated from github.com)
Review

I added a blank line before the if statement

I added a blank line before the if statement
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:07:45 -05:00 (Migrated from github.com)
Review

heh, wonder where that style came from...

heh, wonder where that style came from...
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:09:41 -05:00 (Migrated from github.com)
Review

settings dialog is using camelCase for everything....

I think the Pep8 guidance that "consistency within a file is most important" is a good point here.

I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.

settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most important" is a good point here. I opted to make the new things in SettingsDialogue always use camelCase, but changed the NotificationDialogue be TitleCase.
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
mshafer1 commented 2024-12-21 11:10:10 -05:00 (Migrated from github.com)
Review

renamed

renamed
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
alexhorner commented 2024-12-21 18:57:21 -05:00 (Migrated from github.com)
Review

@alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style?

So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.

> @alexhorner, is there a linter tool or editor config file that I can setup to check code against the desired style? So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).
mshafer1 commented 2024-12-23 15:14:39 -05:00 (Migrated from github.com)
Review

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).

I installed an ran the Rider ide and looked through for additional style changes (and applied the ones that didn't seem to conflict with the previous comments).