toast notifications(+) #17
168
ntfysh_client/NotificationDialog.Designer.cs
generated
@@ -28,90 +28,90 @@
|
||||
/// </summary>
|
||||
private void InitializeComponent()
|
||||
{
|
||||
tbTitle = new System.Windows.Forms.TextBox();
|
||||
button1 = new System.Windows.Forms.Button();
|
||||
tbMessage = new System.Windows.Forms.RichTextBox();
|
||||
iconBox = new System.Windows.Forms.PictureBox();
|
||||
progressBar1 = new System.Windows.Forms.ProgressBar();
|
||||
lbTimeout = new System.Windows.Forms.Label();
|
||||
((System.ComponentModel.ISupportInitialize)iconBox).BeginInit();
|
||||
TxBTitle = new System.Windows.Forms.TextBox();
|
||||
ButtonClose = new System.Windows.Forms.Button();
|
||||
TxBMessage = new System.Windows.Forms.RichTextBox();
|
||||
IconBox = new System.Windows.Forms.PictureBox();
|
||||
ProgressBar1 = new System.Windows.Forms.ProgressBar();
|
||||
LblTimeout = new System.Windows.Forms.Label();
|
||||
((System.ComponentModel.ISupportInitialize)IconBox).BeginInit();
|
||||
SuspendLayout();
|
||||
//
|
||||
// tbTitle
|
||||
// TxBTitle
|
||||
//
|
||||
tbTitle.BackColor = System.Drawing.SystemColors.ControlDark;
|
||||
tbTitle.BorderStyle = System.Windows.Forms.BorderStyle.None;
|
||||
tbTitle.Font = new System.Drawing.Font("Segoe UI", 18F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point);
|
||||
tbTitle.ForeColor = System.Drawing.SystemColors.ControlLightLight;
|
||||
tbTitle.Location = new System.Drawing.Point(54, 13);
|
||||
tbTitle.Name = "tbTitle";
|
||||
tbTitle.ReadOnly = true;
|
||||
tbTitle.Size = new System.Drawing.Size(683, 32);
|
||||
tbTitle.TabIndex = 0;
|
||||
tbTitle.MouseDown += window_MouseDown;
|
||||
TxBTitle.BackColor = System.Drawing.SystemColors.ControlDark;
|
||||
TxBTitle.BorderStyle = System.Windows.Forms.BorderStyle.None;
|
||||
TxBTitle.Font = new System.Drawing.Font("Segoe UI", 18F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point);
|
||||
TxBTitle.ForeColor = System.Drawing.SystemColors.ControlLightLight;
|
||||
TxBTitle.Location = new System.Drawing.Point(54, 13);
|
||||
TxBTitle.Name = "TxBTitle";
|
||||
TxBTitle.ReadOnly = true;
|
||||
TxBTitle.Size = new System.Drawing.Size(683, 32);
|
||||
TxBTitle.TabIndex = 0;
|
||||
TxBTitle.MouseDown += window_MouseDown;
|
||||
//
|
||||
// button1
|
||||
// ButtonClose
|
||||
//
|
||||
button1.BackColor = System.Drawing.SystemColors.ActiveCaptionText;
|
||||
button1.BackgroundImageLayout = System.Windows.Forms.ImageLayout.None;
|
||||
button1.FlatAppearance.BorderColor = System.Drawing.Color.White;
|
||||
button1.FlatAppearance.MouseOverBackColor = System.Drawing.Color.Silver;
|
||||
button1.FlatStyle = System.Windows.Forms.FlatStyle.Popup;
|
||||
button1.ForeColor = System.Drawing.SystemColors.ButtonFace;
|
||||
button1.Location = new System.Drawing.Point(759, 7);
|
||||
button1.Name = "button1";
|
||||
button1.Size = new System.Drawing.Size(29, 38);
|
||||
button1.TabIndex = 1;
|
||||
button1.Text = "X";
|
||||
button1.UseVisualStyleBackColor = false;
|
||||
button1.Click += btnClose_Click;
|
||||
ButtonClose.BackColor = System.Drawing.SystemColors.ActiveCaptionText;
|
||||
ButtonClose.BackgroundImageLayout = System.Windows.Forms.ImageLayout.None;
|
||||
ButtonClose.FlatAppearance.BorderColor = System.Drawing.Color.White;
|
||||
ButtonClose.FlatAppearance.MouseOverBackColor = System.Drawing.Color.Silver;
|
||||
ButtonClose.FlatStyle = System.Windows.Forms.FlatStyle.Popup;
|
||||
ButtonClose.ForeColor = System.Drawing.SystemColors.ButtonFace;
|
||||
ButtonClose.Location = new System.Drawing.Point(759, 7);
|
||||
ButtonClose.Name = "ButtonClose";
|
||||
ButtonClose.Size = new System.Drawing.Size(29, 38);
|
||||
ButtonClose.TabIndex = 1;
|
||||
ButtonClose.Text = "X";
|
||||
ButtonClose.UseVisualStyleBackColor = false;
|
||||
ButtonClose.Click += ButtonClose_ClickHandler;
|
||||
//
|
||||
// tbMessage
|
||||
// TxBMessage
|
||||
//
|
||||
tbMessage.BackColor = System.Drawing.SystemColors.ControlDark;
|
||||
tbMessage.BorderStyle = System.Windows.Forms.BorderStyle.None;
|
||||
tbMessage.Font = new System.Drawing.Font("Segoe UI", 14.25F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point);
|
||||
tbMessage.ForeColor = System.Drawing.SystemColors.ControlLightLight;
|
||||
tbMessage.Location = new System.Drawing.Point(12, 57);
|
||||
tbMessage.Name = "tbMessage";
|
||||
tbMessage.ReadOnly = true;
|
||||
tbMessage.Size = new System.Drawing.Size(776, 191);
|
||||
tbMessage.TabIndex = 2;
|
||||
tbMessage.Text = "";
|
||||
tbMessage.MouseDown += window_MouseDown;
|
||||
TxBMessage.BackColor = System.Drawing.SystemColors.ControlDark;
|
||||
TxBMessage.BorderStyle = System.Windows.Forms.BorderStyle.None;
|
||||
TxBMessage.Font = new System.Drawing.Font("Segoe UI", 14.25F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point);
|
||||
TxBMessage.ForeColor = System.Drawing.SystemColors.ControlLightLight;
|
||||
TxBMessage.Location = new System.Drawing.Point(12, 57);
|
||||
TxBMessage.Name = "TxBMessage";
|
||||
TxBMessage.ReadOnly = true;
|
||||
TxBMessage.Size = new System.Drawing.Size(776, 191);
|
||||
TxBMessage.TabIndex = 2;
|
||||
TxBMessage.Text = "";
|
||||
TxBMessage.MouseDown += window_MouseDown;
|
||||
//
|
||||
// iconBox
|
||||
// IconBox
|
||||
//
|
||||
iconBox.Location = new System.Drawing.Point(12, 12);
|
||||
iconBox.Name = "iconBox";
|
||||
iconBox.Size = new System.Drawing.Size(36, 39);
|
||||
iconBox.TabIndex = 3;
|
||||
iconBox.TabStop = false;
|
||||
IconBox.Location = new System.Drawing.Point(12, 12);
|
||||
IconBox.Name = "IconBox";
|
||||
IconBox.Size = new System.Drawing.Size(36, 39);
|
||||
IconBox.TabIndex = 3;
|
||||
IconBox.TabStop = false;
|
||||
//
|
||||
// progressBar1
|
||||
// ProgressBar1
|
||||
//
|
||||
progressBar1.BackColor = System.Drawing.SystemColors.ControlDarkDark;
|
||||
progressBar1.Enabled = false;
|
||||
progressBar1.ForeColor = System.Drawing.SystemColors.WindowFrame;
|
||||
progressBar1.Location = new System.Drawing.Point(70, 254);
|
||||
progressBar1.MarqueeAnimationSpeed = 1;
|
||||
progressBar1.Name = "progressBar1";
|
||||
progressBar1.Size = new System.Drawing.Size(718, 23);
|
||||
progressBar1.Step = 1;
|
||||
progressBar1.Style = System.Windows.Forms.ProgressBarStyle.Continuous;
|
||||
progressBar1.TabIndex = 4;
|
||||
progressBar1.Value = 100;
|
||||
ProgressBar1.BackColor = System.Drawing.SystemColors.ControlDarkDark;
|
||||
ProgressBar1.Enabled = false;
|
||||
ProgressBar1.ForeColor = System.Drawing.SystemColors.WindowFrame;
|
||||
ProgressBar1.Location = new System.Drawing.Point(70, 254);
|
||||
ProgressBar1.MarqueeAnimationSpeed = 1;
|
||||
ProgressBar1.Name = "ProgressBar1";
|
||||
ProgressBar1.Size = new System.Drawing.Size(718, 23);
|
||||
ProgressBar1.Step = 1;
|
||||
ProgressBar1.Style = System.Windows.Forms.ProgressBarStyle.Continuous;
|
||||
ProgressBar1.TabIndex = 4;
|
||||
ProgressBar1.Value = 100;
|
||||
//
|
||||
// lbTimeout
|
||||
// LblTimeout
|
||||
//
|
||||
lbTimeout.AutoSize = true;
|
||||
lbTimeout.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point);
|
||||
lbTimeout.Location = new System.Drawing.Point(21, 254);
|
||||
lbTimeout.Name = "lbTimeout";
|
||||
lbTimeout.Size = new System.Drawing.Size(43, 17);
|
||||
lbTimeout.TabIndex = 5;
|
||||
lbTimeout.Text = "label1";
|
||||
lbTimeout.TextAlign = System.Drawing.ContentAlignment.TopRight;
|
||||
LblTimeout.AutoSize = true;
|
||||
LblTimeout.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point);
|
||||
LblTimeout.Location = new System.Drawing.Point(21, 254);
|
||||
LblTimeout.Name = "LblTimeout";
|
||||
LblTimeout.Size = new System.Drawing.Size(43, 17);
|
||||
LblTimeout.TabIndex = 5;
|
||||
LblTimeout.Text = "label1";
|
||||
LblTimeout.TextAlign = System.Drawing.ContentAlignment.TopRight;
|
||||
//
|
||||
// NotificationDialog
|
||||
//
|
||||
@@ -119,28 +119,28 @@
|
||||
AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font;
|
||||
BackColor = System.Drawing.SystemColors.ControlDark;
|
||||
ClientSize = new System.Drawing.Size(800, 289);
|
||||
Controls.Add(lbTimeout);
|
||||
Controls.Add(progressBar1);
|
||||
Controls.Add(iconBox);
|
||||
Controls.Add(tbMessage);
|
||||
Controls.Add(button1);
|
||||
Controls.Add(tbTitle);
|
||||
Controls.Add(LblTimeout);
|
||||
Controls.Add(ProgressBar1);
|
||||
Controls.Add(IconBox);
|
||||
Controls.Add(TxBMessage);
|
||||
Controls.Add(ButtonClose);
|
||||
Controls.Add(TxBTitle);
|
||||
FormBorderStyle = System.Windows.Forms.FormBorderStyle.None;
|
||||
Name = "NotificationDialog";
|
||||
Text = "NotificationDialog";
|
||||
Click += window_MouseDown;
|
||||
((System.ComponentModel.ISupportInitialize)iconBox).EndInit();
|
||||
((System.ComponentModel.ISupportInitialize)IconBox).EndInit();
|
||||
ResumeLayout(false);
|
||||
PerformLayout();
|
||||
}
|
||||
|
||||
#endregion
|
||||
|
||||
private System.Windows.Forms.TextBox tbTitle;
|
||||
private System.Windows.Forms.Button button1;
|
||||
private System.Windows.Forms.RichTextBox tbMessage;
|
||||
private System.Windows.Forms.PictureBox iconBox;
|
||||
private System.Windows.Forms.ProgressBar progressBar1;
|
||||
private System.Windows.Forms.Label lbTimeout;
|
||||
private System.Windows.Forms.TextBox TxBTitle;
|
||||
private System.Windows.Forms.Button ButtonClose;
|
||||
private System.Windows.Forms.RichTextBox TxBMessage;
|
||||
private System.Windows.Forms.PictureBox IconBox;
|
||||
private System.Windows.Forms.ProgressBar ProgressBar1;
|
||||
private System.Windows.Forms.Label LblTimeout;
|
||||
}
|
||||
}
|
||||
@@ -39,10 +39,10 @@ namespace ntfysh_client
|
||||
|
|
||||
}
|
||||
|
||||
// setup data
|
||||
iconBox.Image = (icon is null) ? null : ConvertToolTipIconToImage(icon.Value);
|
||||
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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 = (icon is null) ? null : ConvertToolTipIconToImage(icon.Value);
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
|
||||
TxBTitle.Text = title;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
|
||||
TxBMessage.Text = message;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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 (_displayTimeoutTimer != null)
|
||||
@@ -65,7 +65,7 @@ namespace ntfysh_client
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
immediate? immediate?
I try to rename my elements to 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.
I try to rename my elements to 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, 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?
@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?
I'll change the comment to better explain the desired intent rationale: 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).
I'll change the comment to better explain the desired intent rationale: 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).
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.
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.
I went through and attempted to add a blank line before every if 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).
I went through and attempted to add a blank line before every if 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).
changed changed
changed changed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
removed removed
removed removed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
updated updated
updated updated
swapped swapped
swapped swapped
removed removed
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally 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 Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
I installed an ran 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)
|
||||
{
|
||||
|
Nitpick: newline Nitpick: newline
I added a blank line before the if statement I added a blank line before the if statement
|
||||
progressBar1.Value = 100;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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 = 100;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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();
|
||||
_updateTimer.Interval = 100;
|
||||
_updateTimer.Tick += UpdateProgress;
|
||||
@@ -74,20 +74,20 @@ namespace ntfysh_client
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
immediate? immediate?
I try to rename my elements to 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.
I try to rename my elements to 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, 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?
@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?
I'll change the comment to better explain the desired intent rationale: 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).
I'll change the comment to better explain the desired intent rationale: 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).
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.
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.
I went through and attempted to add a blank line before every if 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).
I went through and attempted to add a blank line before every if 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).
changed changed
changed changed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
removed removed
removed removed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
updated updated
updated updated
swapped swapped
swapped swapped
removed removed
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally 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 Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
I installed an ran 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();
|
||||
_shownStopwatch.Start();
|
||||
|
||||
progressBar1.Visible = true;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
|
||||
LblTimeout.Visible = true;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
}
|
||||
else
|
||||
{
|
||||
progressBar1.Visible = false;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
|
||||
LblTimeout.Visible = false;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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
|
||||
{
|
||||
progressBar1.Visible = false;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
|
||||
LblTimeout.Visible = false;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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
|
||||
@@ -99,8 +99,8 @@ namespace ntfysh_client
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
immediate? immediate?
I try to rename my elements to 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.
I try to rename my elements to 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, 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?
@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?
I'll change the comment to better explain the desired intent rationale: 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).
I'll change the comment to better explain the desired intent rationale: 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).
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.
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.
I went through and attempted to add a blank line before every if 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).
I went through and attempted to add a blank line before every if 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).
changed changed
changed changed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
removed removed
removed removed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
updated updated
updated updated
swapped swapped
swapped swapped
removed removed
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally 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 Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
I installed an ran 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 is null) return;
|
||||
|
||||
|
Nitpick: One liner & newline Nitpick: One liner & newline
```csharp
SetWindowPosition();
if (playNotificationSound) PlayNotificationSound();
```
applied applied
|
||||
progressBar1.Value = (int)((_timeout - _shownStopwatch.ElapsedMilliseconds) * 100 / _timeout);
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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}";
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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 = (int)((_timeout - _shownStopwatch.ElapsedMilliseconds) * 100 / _timeout);
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
|
||||
LblTimeout.Text = $"{(int)(_timeout - _shownStopwatch.ElapsedMilliseconds) / 1000}";
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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)
|
||||
@@ -174,7 +174,7 @@ namespace ntfysh_client
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
immediate? immediate?
I try to rename my elements to 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.
I try to rename my elements to 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, 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?
@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?
I'll change the comment to better explain the desired intent rationale: 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).
I'll change the comment to better explain the desired intent rationale: 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).
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.
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.
I went through and attempted to add a blank line before every if 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).
I went through and attempted to add a blank line before every if 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).
changed changed
changed changed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
removed removed
removed removed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
updated updated
updated updated
swapped swapped
swapped swapped
removed removed
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally 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 Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
I installed an ran 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;
|
||||
}
|
||||
|
||||
private void btnClose_Click(object sender, EventArgs e)
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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 ButtonClose_ClickHandler(object sender, EventArgs e)
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the call to the parent class I added a blank line before the call to the parent class
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
|
||||
{
|
||||
// don't animate, immediately "close"
|
||||
Visible = false;
|
||||
@@ -202,15 +202,15 @@ namespace ntfysh_client
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
immediate? immediate?
I try to rename my elements to 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.
I try to rename my elements to 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, 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?
@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?
I'll change the comment to better explain the desired intent rationale: 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).
I'll change the comment to better explain the desired intent rationale: 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).
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.
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.
I went through and attempted to add a blank line before every if 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).
I went through and attempted to add a blank line before every if 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).
changed changed
changed changed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
removed removed
removed removed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
updated updated
updated updated
swapped swapped
swapped swapped
removed removed
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally 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 Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
I installed an ran 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
|
||||
Invoke(new Action(() =>
|
||||
{
|
||||
lbTimeout.Visible = false;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
|
||||
LblTimeout.Visible = false;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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
|
||||
lbTimeout.Visible = false;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
|
||||
LblTimeout.Visible = false;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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;
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent rationale: 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).
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.
I went through and attempted to add a blank line before every if 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).
changed changed
I added a blank line before the if statement I added a blank line before the if statement
removed removed
I added a blank line before the if statement I added a blank line before the if statement
updated updated
swapped swapped
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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
|
||||
|
||||
|
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: One liner? Nitpick: One liner? `if (this.shownStopwatch is null) return;`
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
What's the purpose of this override? What's the purpose of this override?
What's the purpose of this override? What's the purpose of this override?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
This is a great candidate for the new 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
}
```
This is a great candidate for the new 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
}
```
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Lambda one liner Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
Nitpick: Naming convention is capitalised first letter title casing without underscores Nitpick: Naming convention is capitalised first letter title casing without underscores
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
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
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
This appears to be set but never read outside of the This appears to be set but never read outside of the `progress` getter
Could this just read Could this just read `this.progressBar1.Value` instead?
Could this just read Could this just read `this.progressBar1.Value` instead?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Any reason we're wrapping this? Is it protected usually? Any reason we're wrapping this? Is it protected usually?
Does this need Does this need `this`es?
Does this need Does this need `this`es?
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: newline Nitpick: newline
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter Nitpick: Naming convention is capitalised first letter
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
Nitpick: Nitpick: `timeout_ms` should be `timeoutMilliseconds`
immediate? immediate?
immediate? immediate?
I try to rename my elements to 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.
I try to rename my elements to 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, 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?
@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?
I'll change the comment to better explain the desired intent rationale: 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).
I'll change the comment to better explain the desired intent rationale: 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).
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.
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.
I went through and attempted to add a blank line before every if 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).
I went through and attempted to add a blank line before every if 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).
changed changed
changed changed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
removed removed
removed removed
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
updated updated
updated updated
swapped swapped
swapped swapped
removed removed
removed removed
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
yes, I originally thought there would be more to the setter. Removed. yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally though the UI would be Not in the end. Removed. (I had originally 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 Not in the end. Removed. (I had originally though the UI would be `.SetInfo(...); .Show()` or something, but the way it is now has a better expandability and doesn't use this.
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)
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)
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
This got changed to This got changed to `timeoutSeconds` to deal with corresponding comment in `MainForm.cs`
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
I added a blank line before the if statement I added a blank line before the if statement
heh, wonder where that style came from... heh, wonder where that style came from...
heh, wonder where that style came from... heh, wonder where that style came from...
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
settings dialog is using camelCase for everything.... I think the Pep8 guidance that "consistency within a file is most 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.
renamed renamed
renamed renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far 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.
I installed an ran 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).
I installed an ran 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).
|
||||
Nitpick: newline
Nitpick: newline
Nitpick: One liner?
if (this.shownStopwatch is null) return;Nitpick: One liner?
if (this.shownStopwatch is null) return;Nitpick: newline
Nitpick: newline
What's the purpose of this override?
What's the purpose of this override?
Nitpick: newline
Nitpick: newline
This is a great candidate for the new
switch expressionsyntax, and then it can be turned into a lambdaThis is a great candidate for the new
switch expressionsyntax, and then it can be turned into a lambdaNitpick: Lambda one liner
Nitpick: Lambda one liner
Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter title casing without underscores
Nitpick: Naming convention is capitalised first letter title casing without underscores
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
This appears to be set but never read outside of the
progressgetterThis appears to be set but never read outside of the
progressgetterCould this just read
this.progressBar1.Valueinstead?Could this just read
this.progressBar1.Valueinstead?Any reason we're wrapping this? Is it protected usually?
Any reason we're wrapping this? Is it protected usually?
Does this need
thises?Does this need
thises?Nitpick: newline
Nitpick: newline
Nitpick: newline
Nitpick: newline
Nitpick: newline
Nitpick: newline
Nitpick: Naming convention is capitalised first letter
Nitpick: Naming convention is capitalised first letter
Nitpick:
timeout_msshould betimeoutMillisecondsNitpick:
timeout_msshould betimeoutMillisecondsimmediate?
immediate?
I try to rename my elements to 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, 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?
I'll change the comment to better explain the desired intent
rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of 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
rationale:
if a user click the x button, they expect the window to go away "now". My observation is that general Windows users are about 50% split on whether a going away animation in response to telling a window to close is annoying or "fine" (and only a few people "prefer it"). Because of 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 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.
I went through and attempted to add a blank line before every if 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).
changed
changed
I added a blank line before the if statement
I added a blank line before the if statement
removed
removed
I added a blank line before the if statement
I added a blank line before the if statement
updated
updated
swapped
swapped
removed
removed
yes, I originally thought there would be more to the setter. Removed.
yes, I originally thought there would be more to the setter. Removed.
Not in the end. Removed. (I had originally 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.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)
This got changed to
timeoutSecondsto deal with corresponding comment inMainForm.csThis got changed to
timeoutSecondsto deal with corresponding comment inMainForm.csI added a blank line before the if statement
I added a blank line before the if statement
I added a blank line before the if statement
I added a blank line before the if statement
heh, wonder where that style came from...
heh, wonder where that style came from...
settings dialog is using camelCase for everything....
I think the Pep8 guidance that "consistency within a file is most 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.
renamed
renamed
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
So typically I use Rider (alternatively Resharper) whilst working and it picks out most of these things. As far as I know, what it works on is the microsoft standard convention, so I just use that as it's pretty universal and sensible.
I installed an ran 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).