Age | Commit message (Collapse) | Author |
|
|
|
Didn't tested xrandr events with that event detection.
Notify value is 0, the one used (keypress) is 1
|
|
|
|
The output just stopped at some point until a new XEvent was received
As XLockDisplay is in theory a good idea, with XNextEvent blocking its
not usable.
As it turned out, a window can be shared between display connections.
Now the eventloop has its own display connection (which also removes the
need for the lock introduced before).
Additionally the screeninfo doesn't need to be fetched into a TVar in
the eventerloop anymore.
Also this was needed for the signalHandlers to work correctly again.
|
|
*) replaced window destroy and create with a reposition
*) replaced the exception for redraw with an MVar
*) put nextEvent into an own thread, communication over the MVar
*) signal handlers for repositioning and screen swap
Notes:
*) getScreenInfo is a parameter of eventLoop because it blocks when there
is an nextEvent waiting for an new event
|
|
|
|
there is still the bug this plugin needs to be the last or parsing
the config file fails
|
|
|
|
catch alsa exception on decibel acquire
|
|
The last commit removed the exposure event which turned out to be a big
problem.
Although the bug still exists that not all xrandr events are received
when normal events are enabled.
To work around this problem a second display is created on which only
the xrandr events are enabled.
On an exposure event the eventqueue for this display is processed.
The results are very good, in the worst case an exposure event must be
triggered by the user on xmobar to update its position.
|
|
But I'm not sure if something is broken now...
|
|
handle doesn't get all events.
simple c program and simple haskell program are getting all of them.
there must be something in xmobar which catches about 3 of the
screenchange events ...
|
|
This closes #17.
For some reasons the alsa interface does not provide a dB value on all
systems. Instead an error is returned.
The alsa-mixer library checks for such return values and throws an
exception if one is detected.
This patch catches the exception and returns 0 as dB value.
|
|
|
|
|
|
It was only looked for a ']' followed by space-characters and either a
'}' or ','.
This looks good in generally but considering that a command can have as
its last input parameter an array e.g.
...
, Run Something ["Do"]
, Run XMonadLog
]
, sepChar = "%"
}
...
This will not work unless 'Something' is the last command in the array.
This patch fixes this problem, as a ',' is only accepted if it is not
followed by a "Run".
|
|
|
|
|
|
|
|
|
|
As a side-effect, parts without substitution vars will be displayed
as-is, fixing a bug reported by RC in the mailing list.
|
|
|
|
Either due to a change in lm_sensors or in the kernel itself, the core
temperature readings are no longer found in one directory per core but in
multiple files in the same directory. What's worse is that the file names have
little to do with the actual core number. This patch addresses this and is
flexible enough to handle the old layout and the new one.
|
|
src/Plugins/Monitors/Top.hs:140:17:
Illegal bang-pattern (use -XBangPatterns):
! r
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
Brightness Monitor Plugin
|
|
Use 0 if reading the file fails. Fixes issue #13.
|
|
|
|
Thx to mathstuf for the hint
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This solves the common case of a template separator character (such as
{) popping up in xmobar's input (e.g., inside a window title) and
confusing the parser.
|
|
|