summaryrefslogtreecommitdiffhomepage
path: root/src/Xmobar.hs
AgeCommit message (Collapse)Author
2011-09-11Minor cleanupMartin Perner
2011-09-10Wrong value used to check for xrandr eventMartin Perner
Didn't tested xrandr events with that event detection. Notify value is 0, the one used (keypress) is 1
2011-09-10moved signal handler setup into eventloopMartin Perner
2011-09-10removed threading problem with XlibMartin Perner
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.
2011-09-09complete reword of the eventLoopMartin Perner
*) 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
2011-08-31Working versionMartin Perner
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.
2011-08-31Update on Screen change worksMartin Perner
But I'm not sure if something is broken now...
2011-08-30Init commitMartin Perner
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 ...
2011-08-21Show invalid input in case of parsing error in templateJose Antonio Ortega Ruiz
As a side-effect, parts without substitution vars will be displayed as-is, fixing a bug reported by RC in the mailing list.
2011-02-03More XPROPS for the xmobar execJose Antonio Ortega Ruiz
2011-01-22Wee refactoringJose Antonio Ortega Ruiz
2011-01-22Bug fix: don't get confused by align separators in input (issue 14)Jose Antonio Ortega Ruiz
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.
2010-12-27LintingJose Antonio Ortega Ruiz
2010-12-27Bug fix: correctly center text verticallyJose Antonio Ortega Ruiz
2010-12-27Fix for FullBM border specificationJose Antonio Ortega Ruiz
2010-12-27Respect height in BottomSize (issue 27)Jose Antonio Ortega Ruiz
2010-12-21Haskell sources moved to src/ to unclutter toplevelJose Antonio Ortega Ruiz