about summary refs log tree commit diff stats
path: root/util.h
diff options
context:
space:
mode:
authorQuentin Rameau <quinq+hackers@fifth.space>2015-11-07 14:09:08 +0100
committerHiltjo Posthuma <hiltjo@codemadness.org>2015-11-07 14:31:21 +0100
commitdce4fb373757727374d00c857ec0dfd225bbeafd (patch)
tree90d4a9f92b62603cf2bd85fc749db57608b903ab /util.h
parent646b351cc79845f4cc77415dfff474b9ae0053d9 (diff)
downloaddwm-dce4fb373757727374d00c857ec0dfd225bbeafd.tar.gz
setfullscreen: don't process the property twice
Some clients try to set _NET_WM_STATE_FULLSCREEN even when the window is
already in fullscreen.
For example, c->oldstate was set two times in a raw and window would
then always be floating.
We must check that it's not the case before processing it.
(original patch modified with suggestion from Markus Teich
<markus.teich@stusta.mhn.de>)
Diffstat (limited to 'util.h')
0 files changed, 0 insertions, 0 deletions
href='/akkartik/mu/commit/channel.mu?h=main&id=b96af395b9af2ff9df94b3e82213171f30827c8d'>b96af395 ^
9458918f ^
ce87c19e ^
b96af395 ^
ce87c19e ^
b96af395 ^
b0bf5321 ^
ce87c19e ^
b96af395 ^
f192d655 ^
ee72abae ^
b96af395 ^
f192d655 ^
760f683f ^
b96af395 ^
77d5b5d6 ^
4a48bedc ^
b96af395 ^

9458918f ^
5b22547b ^
b96af395 ^
08f4628e ^
b96af395 ^

f192d655 ^
b96af395 ^
f192d655 ^
1ead3562 ^
77d5b5d6 ^
760f683f ^
b96af395 ^
192d59d3 ^

ce87c19e ^

b96af395 ^
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

                                                                
                                                   
                                          
             
             
         
                  
   
                                  
                      
                                                  
                             
 
                         
                 
        
   
            
 
 
                                                           
                                             
             
             

                                      
                                            
                 
                                                  
                                  

        
   
 
 
          
             
                                                                  
                                                                  

                                                

                           
 
# example program: communicating between routines using channels

def producer sink:&:sink:char -> sink:&:sink:char [
  # produce characters 1 to 5 on a channel
  local-scope
  load-inputs
  # n = 0
  n:char <- copy 0
  {
    done?:bool <- lesser-than n, 5
    break-unless done?
    # other threads might get between these prints
    $print [produce: ], n, [ 
]
    sink <- write sink, n
    n <- add n, 1
    loop
  }
  close sink
]

def consumer source:&:source:char -> source:&:source:char [
  # consume and print integers from a channel
  local-scope
  load-inputs
  {
    # read an integer from the channel
    n:char, eof?:bool, source <- read source
    break-if eof?
    # other threads might get between these prints
    $print [consume: ], n:char, [ 
]
    loop
  }
]

def main [
  local-scope
  source:&:source:char, sink:&:sink:char <- new-channel 3/capacity
  # create two background 'routines' that communicate by a channel
  routine1:num <- start-running producer, sink
  routine2:num <- start-running consumer, source
  wait-for-routine routine1
  wait-for-routine routine2
]