Talk:MSI GE75 Raider 8SX
The reason I did not follow the laptop section guidelines for the function key section is because I find the current standard table for it absolutely horrendous; this is not just a subjective opinion, I mean just look at the damn thing!
Visible implies the key can be seen, Marked also implies the key can be seen; how is the reader expected to know which is referring to which?
The proper term for if it is visible to the driver is 'Detected' which is why I used that instead. As for whether or not it is marked, is it not more important than that to know whether or not the key is working? (And well, I just created separate sections for labeled and unlabeled keys, even if that is perhaps, I admit, a little messy)
A bit of an arbitrary decision that one maybe, but that is my reasoning for removing the 'marked' column entirely and replacing it with a column that describes whether it's working or not instead. This will make more sense to most readers than the suggested standard, I have no doubt about this. I understand the need for standards, but if the standards are just outright bad, they're practically made to be broken.
Could I have done a better job? Probably. But I knew I was breaking standard and that someone would take issue with it at some point so I did not bother. Anyone is of course free to convert the section to follow the standard, I will not take any issue with that. But I'm not planning on doing so myself.
Now that this has been brought up and I have given it more thought, if I wanted to improve the current standard (guideline?) this is what I would recommend:
||HW||Yes||Yes||Keyboard Backlighting Increase|
||HW||Yes||Yes||Keyboard Backlighting Decrease|
||No||Yes||No||Gear (Gaming Mode)|
Where Detected is whether or not it is detcted by the system, Labeled is replacing Marked for 'labeled on the keyboard', marked could be fine too that's just semantics really.
And lastly there's a column for whether or not it is working.
This makes a lot more sense since we would have a table that answers all the most important questions at once as opposed to one that.
My final suggestion would be that Effect should be the intended effect of the button rather than the effect that it is by default assigned by the system, since that assignment can be wrong. (Or do you mean to say that it would make more sense for me to leave the 'Effects' section empty for FN+F5 because by default the button is detected as an unassigned keysym and does nothing?)
On another note, about parts of the article being written in first person, I have no real excuse. My priority here is sharing the info and I try to do so in the best quality I can but inevitably something will slip through the cracks from time to time. Editing out the first person bits is perhaps on the menu but I feel I need to actually complete the article first; particularly the audio section. Improving the quality of the article right now is something I feel would be a bit premature because sizable parts of it are still subject to change.