Request 1: Add documentation on how official SumatraPDF releases are compiled

Request 2: Add documentation on the differences between release, prerelease, debug and other builds

Background: I can see that compiled Debug versions have support for making annotations. But they differ from prerelease versions hosted on the website (e.g. they have debug menu items). Do they also diffe

Consider replacing drawStuff() in examples\drawing\drawing.go with the following code:

func testDraw(canvas *walk.Canvas) {
	font, err := walk.NewFont("MS Shell Dlg 2", 12, 0)
	if err != nil {
		panic(err)
	}
	col := walk.RGB(0, 0, 0)
	y := 8
	n := 8
	dx := canvas.Bounds().Width / n
	x := 0
	for i := 0; i < n; i++ {
		format := walk.TextLeft | walk.TextTop
		b := canvas.Bound

Justification
As a convenience to aid support issues, the "friendly" name of the Windows installation should be looked up from the raw version number.

Description
Currently, the RD logs OS version shows as a raw number, e.g.
Operating System: Microsoft Windows NT 6.2.9200.0 x64

Whilst this is technically correct, it's not particular

Because of the switch to GitHub I looked at the ReadMe.txt and it looks really outdated. For example, the whole part with the Archive Support can removed. In general, seems a shortcut to a readme file in the start menu fit the time of Windows XP. Modern programs mostly add now only a shortcut to the program itself, nothing more.

In the first step, I would suggest removing the file from the st

Nice work, definitely a need for a shell between cmd and powershell in complexity. Just by implementing Ctrl-L you've given me a reason to use and promote it!

Many years ago before moving to Unix I used the 4NT shell. It was ten times better than cmd and still is. It's a great example of how to improve on cmd and keep it compatible shell. I lost track of it but I bet the docs are somewhere.

It would be nice to have the documentation hosted online somewhere. Having to download the SDK to view it is inconvenient.

When disabled, accept stdin as-is and don't re-open the TTY. When enabled, accept a user-specified file separator sort of like how cut -d works.

I have a simple Qt window it has a button and when you click the button it opens a explorer window for a specific location, when the notification fades out the window closes as well.

Entire Example Script
`class Example(QWidget):

def __init__(self):
    super().__init__()
    self.initUI()

@pyqtSlot()
def on_click(self):
    print('PyQt5 button click')

Unfortunately, I lost my setup some days ago... and I have no copy of that. So, I decided to redo it, but I'm struggling following the spare guides. I'm trying to reproduce my sticky workspaces setup (three monitors) with no success at all.

The bare template config is:

{
    context.AddBar();
    context.AddFocusIndicator();
    var actionM