mirror of
https://github.com/chatty/chatty.github.io.git
synced 2024-11-08 12:02:28 +01:00
v0.8.6 updates
This commit is contained in:
parent
0ae2562ae2
commit
44218a1e87
28
changes.txt
28
changes.txt
@ -1,5 +1,31 @@
|
||||
|
||||
0.8.5.1 (2017-04-14) Latest Version
|
||||
0.8.6 (2017-05-27) Latest Version
|
||||
|
||||
### General
|
||||
- Added new Notification system
|
||||
- Added support for new sub messages
|
||||
- Added button to sort some setting lists alphabetically
|
||||
- Changed Emote Context Menu entry "Twitch Profile" to "Twitch Stream"
|
||||
- Some other Settings Dialog and GUI improvements
|
||||
- Made Addressbook mod commands channel setting case-insensitive
|
||||
- Some debug output improvements
|
||||
- Updated help
|
||||
|
||||
### Custom Commands
|
||||
- Added custom replacements
|
||||
- Added $ifeq function
|
||||
- Added feature to add channel-specific Custom Commands
|
||||
- Made identifiers case-insensitive
|
||||
- Allow absolute positioning of Custom Menu Items
|
||||
|
||||
### Bugfixes
|
||||
- Fixed word wrapping issues (hopefully)
|
||||
- Fixed selection in chat window moving around
|
||||
- Added workaround for error occuring in Java 1.8.0_131 (the actual cause of the
|
||||
error is still unclear, but hopefully this works well enough)
|
||||
|
||||
|
||||
0.8.5.1 (2017-04-14)
|
||||
|
||||
- Fixed Whispering that didn't work due to changed Twitch behaviour
|
||||
- Fixed bug related to Custom Commands which would prevent startup
|
||||
|
BIN
help/Notifications_example.jpg
Normal file
BIN
help/Notifications_example.jpg
Normal file
Binary file not shown.
After Width: | Height: | Size: 39 KiB |
@ -17,6 +17,7 @@
|
||||
<li><a href="#simple-replacements">Simple Replacements</a></li>
|
||||
<li><a href="#parameters-context">Pre-defined Parameters</a></li>
|
||||
<li><a href="#functions">Functions</a></li>
|
||||
<li><a href="#custom-replacements">Custom Replacements</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
@ -26,6 +27,7 @@
|
||||
<li><a href="#inline-commands">Format 2: Inline-Commands</a></li>
|
||||
<li><a href="#submenus">Format 3: Submenus</a></li>
|
||||
<li><a href="#shortcuts">Shortcuts</a></li>
|
||||
<li><a href="#positioning">Positioning</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
@ -52,6 +54,16 @@
|
||||
<code>Hello World!</code> to chat, just as if you would have written it
|
||||
yourself and pressed Enter.</p>
|
||||
|
||||
<p>Adding a <code>#</code> and a channel name you can restrict the command
|
||||
to that channel:</p>
|
||||
|
||||
<p><code>/hello#joshimuz Hello Joshimuz Chat!</code></p>
|
||||
|
||||
<p>This <code>/hello</code> command would only be executed in #joshimuz,
|
||||
however if you still have the version without a channel in the Custom
|
||||
Commands list as well, it will fallback to that in other channels. This
|
||||
way to can add variations of commands for specific channels.</p>
|
||||
|
||||
<h2><a name="replacements">Replacements</a></h2>
|
||||
<p>Anything starting with <code>$</code> in the <code><what the command
|
||||
should do></code> section is treated as some sort of replacement.
|
||||
@ -205,15 +217,24 @@
|
||||
replacements, however they have a function name before the identifier (there
|
||||
is no short notation for functions):</p>
|
||||
|
||||
<p><code>$<functionName>(<identifier>,<some parameters>)</code></p>
|
||||
<p><code>$<functionName>(<identifier>,<some parameters>,[optional parameters])</code></p>
|
||||
|
||||
<p>The following functions are available:</p>
|
||||
<dl class="defList">
|
||||
<dt><code>$if(<identifier>,<replacement if exists>,<replacement if doesn't exist>)</code></dt>
|
||||
<dt><code>$if(<identifier>,<output if exists>,[output if not])</code></dt>
|
||||
<dd>If the value the identifier refers to exists (non-empty), it will
|
||||
return the first function parameter, the second otherwise.</dd>
|
||||
<dd><em>Example:</em> <code>$if(1,$1,nope)</code> with parameters <code>cheese cake</code> turns into <code>cheese</code>,
|
||||
with no parameters turns into <code>nope</code></dd>
|
||||
<dd><em>Example:</em> <code>$if(1,$1,nope)</code> with command parameters <code>cheese cake</code> turns into <code>cheese</code>,
|
||||
with no parameters turns into <code>nope</code>, the optional <code>[output if not]</code> function parameter.</dd>
|
||||
|
||||
<dt><code>$ifeq(<identifier>,<comparison>,<output if equal>,[output if not])</code></dt>
|
||||
<dd>Similar to <code>$if</code>, but instead of just checking fot the
|
||||
existence of a parameter it compares it to a given value
|
||||
(<code><comparison></code>).</dd>
|
||||
<dd><em>Example:</em> <code>$ifeq(1,cheesecake,yummy)</code> with parameters
|
||||
<code>cheesecake</code> turns into <code>yummy</code>, with parameters
|
||||
<code>cheese cake</code> turns into an an empty string, since the
|
||||
optional <code>[output if not]</code> has not been specified.</dd>
|
||||
|
||||
<dt><code>$join(<identifier>,<separator>)</code></dt>
|
||||
<dd>Joins together the arguments the identifier refers to, using the
|
||||
@ -248,7 +269,28 @@
|
||||
In this example only the closing one after <code>n/a</code> has to be
|
||||
escaped, because the opening one doesn't have a special meaning in this
|
||||
context and the ones around <code>streamuptime</code> have a special
|
||||
meaning that takes precedence (closing the replacement).</p>
|
||||
meaning that takes precedence (opening/closing the replacement).</p>
|
||||
|
||||
<h3><a name="custom-replacements">Custom Replacements</a></h3>
|
||||
<p>You can create your own identifiers for replacements by adding an entry
|
||||
to the Custom Commands list starting with an underscore:</p>
|
||||
|
||||
<p><code>_m $ifeq(1,$(chan),,$$1: )</code></p>
|
||||
|
||||
<p>Instead of a command, this creates an identifier that can be used in a
|
||||
replacement:</p>
|
||||
|
||||
<p><code>/faq $(_m)FAQ: https://pastebin.com/KySx3KDu</code></p>
|
||||
|
||||
<p>When the <code>/faq</code> command is run, the <code>$(_m)</code> gets
|
||||
replaced with whatever is defined in <code>_m</code>, in this case it
|
||||
creates a mention if the first parameter isn't equal to the current
|
||||
channel.</p>
|
||||
|
||||
<p class="note"><em>Note:</em> Custom identifiers always start with an
|
||||
underscore and can themselves not contain replacements with custom
|
||||
identifiers (well they technicially can, but they won't get replaced).</p>
|
||||
|
||||
|
||||
<h2><a name="menus">Custom Context Menus / User Dialog Buttons</a></h2>
|
||||
<p>Under <code>Settings - Commands</code> there are several settings that
|
||||
@ -285,7 +327,12 @@ Spoiler[S]=/timeout $$1 600 No spoilers
|
||||
./Message /Report
|
||||
.Warn User=$$1: Plz no spammerino</pre></div>
|
||||
|
||||
<h3><a name="command-list">Format 1: List Custom Command Names</a></h3>
|
||||
<p class="note"><em>Note:</em> Command Names/Labels may not contain the
|
||||
characters <code>[ ] { }</code> except for their special meaning of
|
||||
<a href="#shortcuts">Shortcuts</a> and <a href="#positioning">Positioning</a>.</p>
|
||||
|
||||
|
||||
<h3><a name="commands-list">Format 1: List Custom Command Names</a></h3>
|
||||
<p>You can list the name of several Custom Commands in one line, for example:</p>
|
||||
|
||||
<p><code>/Slap /Permit</code></p>
|
||||
@ -394,9 +441,10 @@ Spoiler[S]=/timeout $$1 600 No spoilers
|
||||
timeout buttons as well as a single bottom row for the <code>Slap</code>
|
||||
command.</p>
|
||||
|
||||
|
||||
<h3><a name="shortcuts">Shortcuts</a></h3>
|
||||
<p>You can add a shortcut to the end of a label or command name by enclosing
|
||||
it with <code>[ ]</code>:</p>
|
||||
it with <code>[ ]</code> (square brackets):</p>
|
||||
|
||||
<p><code>/Ban[B]</code> or <code>Spoiler[S]=/timeout $$1 ..</code></p>
|
||||
|
||||
@ -423,6 +471,40 @@ Spoiler[S]=/timeout $$1 600 No spoilers
|
||||
allow you to open that submenu by pressing R on your keyboard when the
|
||||
context menu is open).</p>
|
||||
|
||||
|
||||
<h3><a name="positioning">Positioning</a></h3>
|
||||
<p>You can define an absolute position in the menu the entry should appear
|
||||
at by enclosing it with <code>{ }</code> (curly brackets) at the end of
|
||||
the label or command name (but before a shortcut if there is any):</p>
|
||||
|
||||
<p><code>Mention{1}=/insertword $$1: \</code></p>
|
||||
|
||||
<p>This will put the <code>Mention</code> menu entry at the <em>second</em>
|
||||
position in the menu (counting starts from 0).</p>
|
||||
|
||||
<p>Another example:</p>
|
||||
|
||||
<div class="codeblock"><pre>
|
||||
@Twitch Stream[s]
|
||||
.Videos{2}[v]=/openUrlPrompt https://www.twitch.tv/$$1/videos/past-broadcasts
|
||||
@Important{0}
|
||||
.Slap=/me slaps $$1 around a bit with a large trout
|
||||
@Really Important{0}
|
||||
.FAQ=FAQ: https://pastebin.com/KySx3KDu
|
||||
</pre></div>
|
||||
|
||||
<p>This puts the <code>Videos</code> entry into the pre-defined
|
||||
<code>Twitch Stream</code> submenu at the third position in the submenu
|
||||
(also adding the accelerator key <code>s</code> to the menu and
|
||||
<code>v</code> to the entry).</p>
|
||||
|
||||
<p>It also adds the <code>Important</code> submenu at the first position
|
||||
(since it hasn't been added yet) and after that adds the
|
||||
<code>Really Important</code> submenu at the first position as well,
|
||||
moving down <code>Important</code>. This demonstrates that the
|
||||
positioning is based on the current state of the menu, so it can matter
|
||||
<em>when</em> you add entries with absolute positioning.</p>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -33,12 +33,12 @@
|
||||
and add the appropriate parameter after the <code>javaw.exe</code> but
|
||||
before the <code>-jar</code> parameter.</p>
|
||||
|
||||
<p>For example to restrict memory to 100 MB: <code>javaw -Xmx100M -jar "D:\Chatty\Chatty.jar"</code>.
|
||||
100 MB is probably the lowest you should go, although more is recommended,
|
||||
depending on how you are using Chatty (how many/busy channels). Note
|
||||
that Java will show a higher usage than this in the Task Manager, since
|
||||
this pretty much only restricts how much the program can store, Java
|
||||
will need some more for it's own management and data.</p>
|
||||
<p>For example to restrict memory to 150 MB: <code>javaw -Xmx150M -jar "D:\Chatty\Chatty.jar"</code>.
|
||||
You should test out yourself how low you can go, although more than 100 MB
|
||||
is usually recommended. Note that Java will show a higher usage than
|
||||
this in the Task Manager, since this pretty much only restricts how much
|
||||
the program can store, Java will need some more for it's own management
|
||||
and data.</p>
|
||||
|
||||
<p>For the Windows Standalone version you can add this value to the file
|
||||
<code><path to Chatty>/app/Chatty.cfg</code>.</p>
|
||||
|
@ -15,6 +15,7 @@
|
||||
<h1><a name="top">Release Information</a></h1>
|
||||
|
||||
<p>
|
||||
<a href="#0.8.6">0.8.6</a> |
|
||||
<a href="#0.8.5.1">0.8.5.1</a> |
|
||||
<a href="#0.8.5">0.8.5</a> |
|
||||
<a href="#0.8.4.1">0.8.4.1</a> |
|
||||
@ -44,8 +45,49 @@
|
||||
<p>This page shows important information about new versions as well as the
|
||||
full list of changes.</p>
|
||||
|
||||
|
||||
<h2>
|
||||
<a name="0.8.5.1">Version 0.8.5.1</a> <a name="latest">(This one!)</a> (2017-04-14)
|
||||
<a name="0.8.6">Version 0.8.6</a> <a name="latest">(This one!)</a> (2017-05-27)
|
||||
<a href="#top" class="top">[back to top]</a>
|
||||
</h2>
|
||||
<p>This version features a new Notification system, which combines both
|
||||
Desktop Notifications and Sounds. It is more flexible to configure and
|
||||
can be easier extended on the programming side. It has more types of
|
||||
events (like Whispers or AutoMod messages), better matching of events
|
||||
(matching text or restricting to a channel) and things like configurable
|
||||
colors for Desktop Notifications.</p>
|
||||
|
||||
<p><em>Note:</em> While your previous Desktop Notification Settings should be
|
||||
carried over, you will have to reconfigure any Sounds in the new system
|
||||
(if you used any).</p>
|
||||
|
||||
<pre>
|
||||
### General
|
||||
- Added new Notification system
|
||||
- Added support for new sub messages
|
||||
- Added button to sort some setting lists alphabetically
|
||||
- Changed Emote Context Menu entry "Twitch Profile" to "Twitch Stream"
|
||||
- Some other Settings Dialog and GUI improvements
|
||||
- Made Addressbook mod commands channel setting case-insensitive
|
||||
- Some debug output improvements
|
||||
- Updated help
|
||||
|
||||
### Custom Commands
|
||||
- Added custom replacements
|
||||
- Added $ifeq function
|
||||
- Added feature to add channel-specific Custom Commands
|
||||
- Made identifiers case-insensitive
|
||||
- Allow absolute positioning of Custom Menu Items
|
||||
|
||||
### Bugfixes
|
||||
- Fixed word wrapping issues (hopefully)
|
||||
- Fixed selection in chat window moving around
|
||||
- Added workaround for error occuring in Java 1.8.0_131 (the actual cause of the
|
||||
error is still unclear, but hopefully this works well enough)
|
||||
</pre>
|
||||
|
||||
<h2>
|
||||
<a name="0.8.5.1">Version 0.8.5.1</a> (2017-04-14)
|
||||
<a href="#top" class="top">[back to top]</a>
|
||||
</h2>
|
||||
<pre>
|
||||
|
@ -16,7 +16,7 @@
|
||||
| <a href="#Ignore">Ignore</a>
|
||||
| <a href="#Sounds">Sounds</a>
|
||||
| <a href="#Notifications">Notifications</a>
|
||||
| <a href="#Log to file">Log to file</a>
|
||||
| <a href="#Log_to_file">Log to file</a>
|
||||
| <a href="#Window">Window</a>
|
||||
| <a href="#Tabs">Tabs</a>
|
||||
| <a href="#Commands">Commands</a>
|
||||
@ -842,50 +842,104 @@
|
||||
<a name="Sounds">Sounds</a>
|
||||
<a href="#top" class="top">[back to menu]</a>
|
||||
</h2>
|
||||
<h3>General Sound Settings</h3>
|
||||
<p>You can enable or disable all sounds here. Sounds are searched in the
|
||||
displayed folder, which is the current working directory. Any valid sound
|
||||
files in the folder should be selectable as a sound to be played. If you
|
||||
added or removed files, you may have to use <code>Rescan folder</code> to
|
||||
make the files show up in the list. You can open the folder in your standard
|
||||
file browser from here to add files to it more quickly.</p>
|
||||
|
||||
<p>The <strong>Output Device</strong> lets you choose the device on your
|
||||
computer the sounds gets output to. This is kind of experimental and may
|
||||
not work properly.</p>
|
||||
|
||||
<h3>Sound Types Settings</h3>
|
||||
<p>You can specify requirements, soundfile, volume and delay for
|
||||
different types of events:</p>
|
||||
<ul>
|
||||
<li>When a message is highlighted</li>
|
||||
<li>When a stream changes status (online/offline/changed title/changed game)</li>
|
||||
<li>When any message in received in any open channel</li>
|
||||
<li>When someone joins/leaves any open channel</li>
|
||||
<li>When a new follower is detected <em>(this only works if the <a href="help.html#followers">Follower
|
||||
Dialog</a> is currently open)</em></li>
|
||||
</ul>
|
||||
<p>You can set a delay (seconds) so that the same sound won't be played twice during
|
||||
the set number of seconds. So if e.g. 3 highlighted messages come in within
|
||||
10 seconds and the delay is set to 15 seconds, only one sound will be played.</p>
|
||||
|
||||
<p>Each sound has different options for when the sound should be played. See
|
||||
the <a href="#Notifications">Notification Settings</a> for help on the options.</p>
|
||||
<p>Sounds are now integrated into the <a href="#Notifications">Notifications</a>.</p>
|
||||
|
||||
<h2>
|
||||
<a name="Notifications">Notifications</a>
|
||||
<a href="#top" class="top">[back to menu]</a>
|
||||
</h2>
|
||||
<h3>Notifications</h3>
|
||||
<p>You can show notifications for two kinds of things:</p>
|
||||
<ul>
|
||||
<li><strong>Highlights</strong> - When a message in chat is highlighted</li>
|
||||
<li><strong>Stream Status</strong> - When a stream changes status, e.g.
|
||||
offline -> online or changed title</li>
|
||||
</ul>
|
||||
<p>The <strong>Events</strong> table can contain several entries that
|
||||
describe events and whether they should trigger a Desktop Notification
|
||||
and/or Sound.</p>
|
||||
|
||||
<p>The entries are checked from the top and only the first enabled
|
||||
Notification and Sound of matching events are chosen, and then triggered
|
||||
if the Cooldowns allow it (given that any are configured).</p>
|
||||
|
||||
<p>Example: You could have two "Highlights" events, the first restricted to
|
||||
a certain channel with a Notification/Sound and the second
|
||||
non-restricted with just a Notification. This way only Highlights in
|
||||
said channel would play a Sound (and maybe have different Notification
|
||||
colors) and all others just show a Notification. Note that if you were
|
||||
to switch those entries, then the channel-restricted one would never be
|
||||
chosen, because the non-restricted one already catches everything. So as
|
||||
a general rule, the more specific/restricted entries should always come
|
||||
first.</p>
|
||||
|
||||
<p><img src="Notifications_example.jpg" /></p>
|
||||
|
||||
<p>Possible event types that can be selected for an entry:</p>
|
||||
|
||||
<dl class="dl-settings">
|
||||
<dt>Stream Status</dt>
|
||||
<dd>A stream Chatty is watching (because you have it's chat open
|
||||
or you follow it) went online/offline or changed title.</dd>
|
||||
|
||||
<dt>Highlights</dt>
|
||||
<dd>Chat Messages that were highlighted.</dd>
|
||||
|
||||
<dt>Chat Message</dt>
|
||||
<dd>Any Chat Message (including highlighted ones, in this case
|
||||
the order of list entries can matter).</dd>
|
||||
|
||||
<dt>Whisper</dt>
|
||||
<dd>Any Whisper message (including highlighted ones).</dd>
|
||||
|
||||
<dt>User Joined & User Left</dt>
|
||||
<dd>When a user is seen entering or leaving a chat. Note that
|
||||
this is quite unreliable, see <a href="help.html#userlist">Userlist and JOIN/PART</a>.</dd>
|
||||
|
||||
<dt>New Followers</dt>
|
||||
<dd>When a new follower is detected <em>(this only works if the
|
||||
<a href="help.html#followers">Follower Dialog</a> is
|
||||
currently open)</em>.</dd>
|
||||
|
||||
<dt>Subscriber Notification</dt>
|
||||
<dd>When a new Subscriber/Resub notification is received in chat.</dd>
|
||||
|
||||
<dt>AutoMod Message</dt>
|
||||
<dd>When a new chat message filtered by AutoMod is received.</dd>
|
||||
</dl>
|
||||
|
||||
<h3>Settings for an entry (Notification/Sound)</h3>
|
||||
<dl class="dl-settings">
|
||||
<dt>Channel</dt>
|
||||
<dd>Name of the channel this item should be restricted to.</dd>
|
||||
|
||||
<dt>Match</dt>
|
||||
<dd>Match the given text or message, in the same format as for
|
||||
<a href="#Highlight">Highlighting</a> (although some prefixes won't
|
||||
work unless it's a chat message).</dd>
|
||||
|
||||
<dt>Notification (Tab)</dt>
|
||||
<dd>A Desktop Notification, with customizable colors.</dd>
|
||||
|
||||
<dt>Sound (Tab)</dt>
|
||||
<dd>Play the selected Sound.</dd>
|
||||
<dd>Specify a <code>Cooldown</code> to prevent this sound from playing
|
||||
too often.</dd>
|
||||
<dd><code>Passive Cooldown</code> will only play the sound if enough
|
||||
time has passed since this event was last matched. Or in other words
|
||||
it will reset the Cooldown every time the sound <em>would</em> have
|
||||
been played, even if it actually wasn't because another sound took
|
||||
precedence or the regular <code>Cooldown</code> didn't allow it.</dd>
|
||||
<dd>For example if your chat isn't very busy and you want to get
|
||||
notified of new messages so you notice, then you could add an event
|
||||
of type <code>Chat Message</code> with a <code>Passive Cooldown</code>
|
||||
of <code>5m</code>, which means the sound only plays if someone
|
||||
writes a message after the chat has been silent for at least 5 minutes.
|
||||
If on the other hand you would set it as a regular <code>Cooldown</code>
|
||||
it would play the sound after 5 minutes even if the chat has been
|
||||
busy non-stop, at which point you probably wouldn't need to be alerted
|
||||
since you're already paying attention to it.</dd>
|
||||
</dl>
|
||||
|
||||
<p>On both the <strong>Notification (Tab)</strong> and <strong>Sound (Tab)</strong>
|
||||
you can enable/disable the according action by choosing one of the
|
||||
following:</p>
|
||||
|
||||
<p>For both these you can select separately if and when they are shown:</p>
|
||||
<ul>
|
||||
<li><strong>Enabled</strong> - No requirements, always show it</li>
|
||||
<li><strong>Off</strong> - Never show</li>
|
||||
<li><strong>When channel/app not active</strong> - Only when the channel
|
||||
isn't the currently selected tab AND when the program doesn't have focus</li>
|
||||
@ -897,44 +951,53 @@
|
||||
isn't the currently selected tab</li>
|
||||
<li><strong>When channel active</strong> - Only when the channel IS the
|
||||
currently selected tab</li>
|
||||
<li><strong>Always</strong> - No requirements, always show it</li>
|
||||
</ul>
|
||||
|
||||
<p>In addition, the option <strong>Don't notify about "Stream offline"</strong> allows you
|
||||
to never show when a stream changes status to offline, so you will only be
|
||||
notified about streams going live or changing title/game.</p>
|
||||
|
||||
<h3>Notification Type / Options</h3>
|
||||
<p>Select here whether to use the <em>Chatty Notifications</em> or the default
|
||||
<em>System Tray Notifications</em>. This settings DOES NOT enable or
|
||||
disable notifications altogether, just switch between the types.</p>
|
||||
<p>If you have <em>Chatty Notifications</em> selected, you can change some
|
||||
more options:</p>
|
||||
<ul>
|
||||
<li><strong>Position:</strong> In which corner the the notification appears on the screen</li>
|
||||
<li><strong>Screen:</strong> On which screen the notification appears (<code>auto</code> means
|
||||
it's on the same screen as the Chatty window)</li>
|
||||
<li><strong>Display Time:</strong> How long the notification will be displayed
|
||||
by default. This can vary a bit depending on the situation.</li>
|
||||
<li><strong>No User Activity:</strong> This is a tricky one. If you enable
|
||||
this, then the notification will not be closed after the defined Display Time
|
||||
if no activity was detected in the last few seconds. This can be useful
|
||||
to still see notifications from a few minutes ago if you were away from
|
||||
the computer.
|
||||
The time defines
|
||||
when the notification will be closed no
|
||||
matter what, so older notifications won't stay there forever if you are
|
||||
away from the computer for a bit longer.
|
||||
<br /><br />Activity is tracked through two methods:
|
||||
The first method is tracking the system-wide mouse movements, which is
|
||||
done through an API that may not always return accurate information
|
||||
(e.g. if you are in a game) and it only checks the position every few
|
||||
seconds (only the last location is saved at any time for comparison).
|
||||
The second method detects activity only inside of Chatty, by tracking
|
||||
button presses and mouse actions (e.g. if you type a message, open a
|
||||
dialog etc.).</li>
|
||||
<h3>General Notification Settings</h3>
|
||||
<dl class="dl-settings">
|
||||
<dt>Position</dt>
|
||||
<dd>The corner of the screen the notification is displayed.</dd>
|
||||
|
||||
</ul>
|
||||
<dt>Screen</dt>
|
||||
<dd>On which screen the notification appears (auto means it's on the
|
||||
same screen as the Chatty window).</dd>
|
||||
|
||||
<dt>Display Time</dt>
|
||||
<dd>How long the notification will be displayed by default. This can
|
||||
vary a bit depending on the situation.</dd>
|
||||
|
||||
<dt>No User Activity</dt>
|
||||
<dd>This is a tricky one. If you enable this, then the notification will
|
||||
not be closed after the defined Display Time if no activity was
|
||||
detected in the last few seconds. This can be useful to still see
|
||||
notifications from a few minutes ago if you were away from the
|
||||
computer. The time defines when the notification will be closed no
|
||||
matter what, so older notifications won't stay there forever if you
|
||||
are away from the computer for a bit longer.</dd>
|
||||
<dd>Activity is tracked through two methods: The first method is
|
||||
tracking the system-wide mouse movements, which is done through an
|
||||
API that may not always return accurate information (e.g. if you are
|
||||
in a game) and it only checks the position every few seconds (only
|
||||
the last location is saved at any time for comparison). The second
|
||||
method detects activity only inside of Chatty, by tracking button
|
||||
presses and mouse actions (e.g. if you type a message, open a dialog
|
||||
etc.).</dd>
|
||||
</dl>
|
||||
|
||||
<h3>General Sound Settings</h3>
|
||||
<p>You can enable or disable all sounds here. Sounds are searched in the
|
||||
displayed folder, which is the current working directory, although you can
|
||||
also <code>Change</code> it to a folder of your choice. If you added or removed files,
|
||||
you may have to use <code>Rescan folder</code> to make the files show up in
|
||||
the list of sounds selectable in the event settings. You can <code>Open</code>
|
||||
the folder in your standard file browser from here to add files to it more
|
||||
quickly.</p>
|
||||
|
||||
<p>The <strong>Output Device</strong> lets you choose the device on your
|
||||
computer the sounds gets output to. This is kind of experimental and may
|
||||
not work properly.</p>
|
||||
|
||||
<h3>Followed Streams</h3>
|
||||
<p>Enable this to make Chatty get a list of your followed streams regulary
|
||||
so it can display notifications if their status changes. This simpy allows
|
||||
@ -942,6 +1005,7 @@
|
||||
advantage. It also allows it to record the viewer count and status history
|
||||
of followed live streams as long as Chatty is running.</p>
|
||||
|
||||
|
||||
<h2>
|
||||
<a name="Log_to_file">Log to file</a>
|
||||
<a href="#top" class="top">[back to menu]</a>
|
||||
@ -1130,7 +1194,15 @@
|
||||
scroll through them.</dd>
|
||||
|
||||
<dt>Scroll through tabs with mousewheel</dt>
|
||||
<dd>Hover mouse over tabs and scroll to change tabs.</dd>
|
||||
<dd>Hover mouse over tabs and scroll to change tabs.
|
||||
<dl class="dl-settings-sub">
|
||||
<dt>Scroll through tabs anywhere</dt>
|
||||
<dd>Don't restrict scrolling through tabs to the tab bar,
|
||||
although this mostly only applies to the inputbox. So you
|
||||
can hover your mouse over the inputbox and scroll to switch
|
||||
between tabs.</dd>
|
||||
</dl>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
<h2>
|
||||
|
@ -5,7 +5,7 @@
|
||||
<link rel="stylesheet" type="text/css" href="style.css" />
|
||||
</head>
|
||||
<body>
|
||||
<h1><a name="top">Chatty (Version: 0.8.5.1)</a></h1>
|
||||
<h1><a name="top">Chatty (Version: 0.8.6)</a></h1>
|
||||
<table>
|
||||
<tr>
|
||||
<td valign="top">
|
||||
|
12
index.html
12
index.html
@ -15,9 +15,9 @@ function loaded() {
|
||||
{ ceiling: null, text: "$years years ago" }
|
||||
]
|
||||
}
|
||||
document.getElementById("ago").innerHTML = "Version 0.8.5.1 released "+humanized_time_span("2017/04/14", Date(), custom_date_formats)+"";
|
||||
document.getElementById("ago").innerHTML = "Version 0.8.6 released "+humanized_time_span("2017/05/27", Date(), custom_date_formats)+"";
|
||||
|
||||
getDownloads("v0.8.5.1");
|
||||
getDownloads("v0.8.6");
|
||||
}
|
||||
|
||||
function getDownloads(tag) {
|
||||
@ -217,15 +217,15 @@ function getDownloads(tag) {
|
||||
|
||||
<h2 id="download">Download & Getting started</h2>
|
||||
<ul>
|
||||
<li><a href="https://github.com/chatty/chatty/releases/download/v0.8.5.1/Chatty_0.8.5.1.zip"><strong>Download Version 0.8.5.1</strong></a>
|
||||
<li><a href="https://github.com/chatty/chatty/releases/download/v0.8.6/Chatty_0.8.6.zip"><strong>Download Version 0.8.6</strong></a>
|
||||
(all OS)</li>
|
||||
<li>With global hotkey support (Windows only):<ul>
|
||||
<li><a href="https://github.com/chatty/chatty/releases/download/v0.8.5.1/Chatty_0.8.5.1_hotkey_32bit.zip">Download Version 0.8.5.1 (for 32bit-Java)</a>
|
||||
<li><a href="https://github.com/chatty/chatty/releases/download/v0.8.6/Chatty_0.8.6_hotkey_32bit.zip">Download Version 0.8.6 (for 32bit-Java)</a>
|
||||
</li>
|
||||
<li><a href="https://github.com/chatty/chatty/releases/download/v0.8.5.1/Chatty_0.8.5.1_hotkey_64bit.zip">Download Version 0.8.5.1 (for 64bit-Java)</a>
|
||||
<li><a href="https://github.com/chatty/chatty/releases/download/v0.8.6/Chatty_0.8.6_hotkey_64bit.zip">Download Version 0.8.6 (for 64bit-Java)</a>
|
||||
</li>
|
||||
</ul></li>
|
||||
<li>Standalone Bundle (Windows executable, includes JRE, no installed Java required):<ul><li><a href="https://github.com/chatty/chatty/releases/download/v0.8.5.1/Chatty_0.8.5.1_windows_standalone.zip">Download Version 0.8.5.1 Windows Standalone</a></li></ul></li>
|
||||
<li>Standalone Bundle (Windows executable, includes JRE, no installed Java required):<ul><li><a href="https://github.com/chatty/chatty/releases/download/v0.8.6/Chatty_0.8.6_windows_standalone.zip">Download Version 0.8.6 Windows Standalone</a></li></ul></li>
|
||||
<li>Previous versions and source code are on <a href="https://github.com/chatty/chatty/releases">GitHub</a></li>
|
||||
</ul>
|
||||
|
||||
|
@ -1 +1 @@
|
||||
0.8.5.1 Some Bugfixes
|
||||
0.8.6 New Notification system, Bugfixes, and more..
|
||||
|
Loading…
Reference in New Issue
Block a user