Changes Initial release

Downloads

MacOS

Linux

Windows

The official post about this topic hasn't been updated in a long while. So here is a short wizard friendly refresh.

For all users

Creating a startup shortcut to the common start menu Startup folder requires the installer to be run in administrative installation mode, if not done through the wizard add the following line to the Setup block.

[Setup]
PrivilegesRequired=admin

Assuming that that the following compiler directives are defined '#MyAppName' and '#MyAppExeName', normally done in the very last step of the script wizard, append the following line to the Icons segment.

[Icons]
Name: "{commonstartup}\{#MyAppName}"; Filename: "{app}\{#MyAppExeName}"

The 'commonstartup' points to

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup

For user (installer) only

No administrative installation mode is required here. As before presuming you have the defined directives, in the Icons block.

[Icons]
Name: "{userstartup}\{#MyAppName}"; Filename: "{app}\{#MyAppExeName}"

'userstartup' leads to

C:\Users\__Username__\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

As of xrandr version 1.5 it has become easy to divide your physical monitors into smaller virtual monitors. This is done with the following commands (without the '' quotation marks), scroll down for examples, explanations and even further down for more information.

xrandr --setmonitor 'vn' 'vw'/'pw'x'vh'/'ph'+'wo'+'ho' 'od'
This commands creates a virtual monitor

vn virtual monitor name
vw virtual monitor width in pixels
pw physical width on monitor in milimeters
vh virtual monitor height in pixels
ph physcical heigt on monitor in milimeters
wo width offset of the virutal monitor
ho height offset of the virtual monitor
od output device, the physical monitor on which the virtual monitor will be projected, specify none if your previous virtual entry is projected on the same monitor

xrandr --fb 'tw'x'th'
This command sets the total resolution of all the screens

tw The total width off all virtual monitors + their width offsets combined
th The total height off all virtual monitors + their height offsets combined

xrandr --delmonitor 'vn'
This command deletes a monitor

vn virtual monitor name

Identify your monitors(s)

Run the command xrandr in your terminal, you should see a list with all your output devices and for connected devices their supported modi. For my system it looks like this (shortened);

$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DVI-D-1 disconnected (normal left inverted right x axis y axis)
VGA-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 476mm x 268mm
...
VGA-1-1 connected (normal left inverted right x axis y axis)
...
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 connected (normal left inverted right x axis y axis)
...

We can see I have three monitors connected on my system, but only one is turned on and displaying, that is VGA-2.
As you may notice it looks like a virtual screen which xrandr created by default, lets look closer.

Errors

Some errors which I encountered during building 'systray' (github.com/getlantern/systray)

Package xapp was not found in the pkg-config search path.
Perhaps you should add the directory containing `xapp.pc'
to the PKG_CONFIG_PATH environment variable

running gcc failed: exit status 1
/usr/bin/ld: cannot find -lxapp
collect2: error: ld returned 1 exit status

Solution

Simply install the missing package with

sudo apt-get install libxapp-dev 

You probably just installed the whole Flutter by following the getting started guide neatly, and see your build of the test app getting stuck at "Initializing graddle...".

Do note that the first launch of graddle will take some time, even on a good computer and fast internet (for me it was around 20 minutes).

Before you stop and try to rebuild, I suggest you enable verbose building output. (Scroll down) so you see what is actually happening.

Also make sure you have set your system PATH correctly.

Problem:

You probably want to tell users on your page to wait for something important that is happening in the background. Most likely performing asynchronous page calls, calculations, DOM manipulation etc...

But just like any CSS property, the nested elements override the parent's property. This is troublesome if you have a lot of buttons and custom cursors in your style.