Hotkey Setup - Proopai/eve-o-preview GitHub Wiki

It is possible to set a key combinations to immediately jump to certain EVE window. However currently EVE-O Preview doesn't provide any GUI to set the these hotkeys. It should be done via editing the configuration file directly. Don't forget to make a backup copy of the file before editing it.

Note: Don't forget to make a backup copy of the file before editing it.

Open the file using any text editor. find the entry ClientHotkey. Most probably it will look like

"ClientHotkey": {},

This means that no hotkeys are defined. Edit it to be like

"ClientHotkey": {
  "EVE - Phrynohyas Tig-Rah": "F1",
  "EVE - Ondatra Patrouette": "F2"
}

This simple edit will assign F1 as a hotkey for Phrynohyas Tig-Rah and F2 as a hotkey for Ondatra Patrouette, so pressing F1 anywhere in Windows will immediately open EVE client for Phrynohyas Tig-Rah if he is logged on.

The following hotkey is described as modifier+key where modifier can be Control, Alt, Shift, or their combination. F.e. it is possible to setup the hotkey as

"ClientHotkey": {
  "EVE - Phrynohyas Tig-Rah": "F1",
  "EVE - Ondatra Patrouette": "Control+Shift+F4"
}

Note: Do not set hotkeys to use the key combinations already used by EVE. It won't work as "I set hotkey for my DPS char to F1 and when I'll press F1 it will automatically open the DPS char's window and activate guns". Key combination will be swallowed by EVE-O Preview and NOT retranslated to EVE window. So it will be only "it will automatically open the DPS char's window".

In a similar pattern to the per client Hotkey Setup, It is possible to set a key combinations to cycle through select Eve Windows. EVE-O Preview doesn't provide any GUI to set the these hotkeys. It should be done via editing the configuration file directly. Don't forget to make a backup copy of the file before editing it.

If you have not run EVE-O Preview before, or since this feature was added then it is recommended to quickly open and close EVE-O Preview once to trigger the config to update with some sample values.

Note: Don't forget to make a backup copy of the file before editing it.

Open the file using any text editor. find the entries CycleGroup1ForwardHotkeys and CycleGroup1BackwardHotkeys. Most probably it will look like

"CycleGroup1ForwardHotkeys": [
  "F14",
  "Control+F14"
],
"CycleGroup1BackwardHotkeys": [
  "F13",
  "Control+F13"
]

Note: It is highly recommended to leave the Hotkey values as default and bind them with a gaming device if you can support it.

Next find the entry CycleGroup1ForwardHotkeys. Most probably it will look like

"CycleGroup1ClientsOrder": {
  "EVE - Example DPS Toon 1": 1,
  "EVE - Example DPS Toon 2": 2,
  "EVE - Example DPS Toon 3": 3
}

You should modify this entry with a list of each of your clients replacing "Example DPS Toon 1", etc with the name of your character. The numbers on the right are used to force the order in which they cycle. If a character appears in the list but is not currently logged in, then it will simply be skipped. If a character does not appear in the list, then they will never become active when cycling clients.

By now you may have noticed that there are two groups. The above configuration can be followed for a second group by using the values CycleGroup2ForwardHotkeys, CycleGroup2BackwardHotkeys, and CycleGroup2ForwardHotkeys This may provide useful if you want to have one HotKey to cycle through a group of DPS characters, while another HotKey cycles through support roles such as gate scouts, or a group of logi.

Alternatively you may not want to use any of these HotKeys. Please note that deleting the values in their entirety will simply result in them being automatically re-generated. Should you wish to remove these HotKeys completely, Simply set the values to empty, such as the example below:

  "CycleGroup1ForwardHotkeys": [],
  "CycleGroup1BackwardHotkeys": [],
  "CycleGroup1ClientsOrder": {},
  "CycleGroup2ForwardHotkeys": [],
  "CycleGroup2BackwardHotkeys": [],
  "CycleGroup2ClientsOrder": {}

Hints

• Minimise the use of modifiers or standard keys to minimise issues with the client playing up. In the default example unusual Function keys (e.g. F14) are used which are then bound to a game pad or gaming mouse.
• The Eve client can be somewhat less than stable, often getting confused as client focus switches. It is near certain that you will experience issues such as keys sticking or even in some cases D-Scan running each time the client swaps. So far I have found no perfect solution and opt for the most stable solution instead, of sticking to the F14+ keys.
• For the best experience try to use the Control modifier. In the default example F14 is used to cycle to the next client, but if pressed mid locking a target (Control + Clicking) then the client will not cycle. By registering Control+F4 as an additional hotkey, the client will cycle.
• For a list of supported keys, see: https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.keys

Have you ever wanted your main client to show up in a different color so that it more easily catches your eye? Or maybe your Logi to stand out?

EVE-O Preview doesn't provide any GUI to set the these per client overrides as yet. Though, It can be done via editing the configuration file directly. Note Don't forget to make a backup copy of the file before editing it.

Open the file using any text editor. find the entry PerClientActiveClientHighlightColor. Most probably it will look like

"PerClientActiveClientHighlightColor": {
  "EVE - Example Toon 1": "Red",
  "EVE - Example Toon 2": "Green"
}

You should modify this entry with a list of each of your clients replacing "Example Toon 1", etc with the name of your character. The names on the right represent which highligh color to use for that clients border.

If a client does not appear in this list, then it will use the global highlight color by default.

Hint For a list of supported colors see: https://docs.microsoft.com/en-us/dotnet/api/system.drawing.color#properties

This setting allows to enable an alternate thumbnail render. This render doesn't use advanced DWM API to create live previews. Instead it is a screenshot-based render with the following pros and cons:

• + Should work even in remote desktop environments
• - Consumes significantly more memory. In the testing environment EVE-O Preview did consume around 180 MB to manage 3 thumbnails using this render. At the same time the primary render did consume around 50 MB when run in the same environment.
• - Thumbnail images are refreshed at 1 FPS rate
• - Possible short mouse cursor freezes