4636eb840d
fix compilation with older xcb-util with -DXCB_COMPAT (Thanks okraits)
2012-09-03 14:55:27 +02:00
a007283773
i3-input: Fix text drawing offset
2012-08-28 12:06:03 +02:00
af15087b99
i3-input: Do not use a non-loaded font
...
We must call load_font before any font-related calls like
predict_text_width
2012-08-28 10:58:18 +02:00
2896ae8057
logging: make libi3 use verboselog()/errorlog(), provide it in each caller
...
While this is a bit ugly, it makes the log messages end up where they
are supposed to: in the shmlog/stdout in case of i3 and on stdout in
case of utilities such as i3-input
2012-08-13 13:27:16 +02:00
6ff3f7abad
libi3: Implement Pango rendering
2012-08-13 11:39:30 +02:00
210fc6dfed
libi3: Rework predict_text_width
...
predict_text_width now takes an i3String as argument
2012-08-13 11:37:23 +02:00
53365fa887
libi3: Rework draw_text
...
We now have two versions of draw_text
draw_text: Now takes an i3String
draw_text_ascii: Designed for static strings in plain ASCII
2012-08-13 11:37:21 +02:00
284294e9c2
i3-input: Store and use xcb_char2b_t directly
2012-08-13 11:30:08 +02:00
d89cb04c98
i3-input: Port prompt to i3String
2012-08-13 11:30:08 +02:00
b01545b131
Makefile: Always link libi3 first
2012-08-13 02:00:01 +02:00
8a1c8115ca
fix a few warnings/places where the clang static analyzer complains
2012-08-05 16:34:38 +02:00
0b4ee7a1da
common.mk: Split XCB common flags
2012-07-23 00:12:55 +02:00
5e0cd52f10
common.mk: Split XCB keyboard flags
2012-07-23 00:06:37 +02:00
c7029a5e21
common.mk: Introduce I3_*FLAGS
...
CPPFLGES, CFLAGS and LDFLAGS should be user variables
We now provide default flags but use I3_*FLAGS flags for our own needed
flags
Also reoder lib flags a bit
2012-07-22 23:53:49 +02:00
3b1b72ecbb
*.mk: Support passing specific CFLAGS/LIBS
2012-07-22 23:53:13 +02:00
e452acb30e
Add stub Makefiles to allow subdir make calls
2012-07-22 19:57:48 +02:00
eb08d33692
Move i3-input to the new Makefile layout
2012-07-22 19:57:21 +02:00
dee7c07ad2
shmlog: store meta information in the buffer itself, store path as X11 atom
...
This makes i3-dump-log completely independent of a running i3 instance.
2012-01-06 23:40:07 +00:00
561cf3719f
little style fixes
2011-11-21 21:48:24 +00:00
344c04af12
Implement set_font_colors.
...
This paves the way for other font rendering backends. Fonts and
colors shouldn't be specified manually from now on.
2011-11-21 20:52:32 +00:00
eafc7af606
Make all programs use draw_text.
2011-11-21 20:52:29 +00:00
fb11cc2d14
Consolidate all convert_* functions into libi3.
...
Some minor fixes along the way as well. Very minor stuff, unlikely
to ever be visible to the user.
2011-11-16 20:54:30 +00:00
d5613905c8
Plug minor leaks in string conversion routines.
2011-11-07 19:57:11 +00:00
726f2a1e5a
normalize file headers across **/*.{h,c}
2011-10-25 21:19:38 +01:00
f4469eee0b
get rid of xcb.c in all i3-* tools
...
open_input_window was slightly different for each of them, so it made no sense
to generalize it (then we would end up with a thin and useless wrapper).
2011-10-23 23:20:57 +01:00
a58018cf66
Add libi3/load_font, use it everywhere
...
…except for i3bar, which needs slightly more information about the font
2011-10-23 22:37:11 +01:00
c2d04116d4
i3-input: Remove unused get_mod_mask from xcb.c
2011-10-23 19:37:28 +01:00
05d097bb36
i3-input: fix handling of Mode_switch (makes special characters work again)
...
This seems to have only worked before in certain settings, where the modifiers
were configured in a way that it matched by chance…
2011-10-23 19:34:48 +01:00
7c04e23ab7
i3-input: Bugfix: font must be dynamically allocated, we FREE it later
2011-10-23 19:34:21 +01:00
6dc6ba11fc
Eliminate xcb_change_gc_single everywhere with C99
2011-10-23 18:06:25 +01:00
cb9bbcfccf
Move get_colorpixel to libi3, use it everywhere else
2011-10-23 17:38:21 +01:00
0086bcb2b4
i3-input: eliminate xcb_change_gc_single usage with C99
2011-10-23 17:26:06 +01:00
4f57d49318
add libi3/ipc_connect, use it in i3-config-wizard, i3-input, i3bar
2011-10-23 17:18:14 +01:00
9d15a00ba8
introduce sasprintf() in libi3, use it everywhere
2011-10-23 13:16:56 +01:00
d87b0f13a0
i3-input: use IPC functions from libi3
2011-10-23 13:15:20 +01:00
4f6e58e250
Makefiles: prefix compilation messages (for parallel builds)
2011-10-02 16:04:18 +01:00
1737a78fcd
i3-input: implement -F (format) option, deprecate -p (prefix)
...
This introduces the '-F format' parameter, which takes a format and replaces %s
in it with the user input. An example: The user should enter the target
workspace name. The appropriate i3-input invocation looks like this:
i3-input -F 'workspace "%s"' -P 'Switch to workspace: '
2011-09-18 13:51:11 +01:00
fddee471e8
i3-input: add missing \n in --help
2011-09-18 13:21:45 +01:00
46ab86b88d
i3-input: reformat main.c
2011-09-18 13:20:59 +01:00
6a07e08320
makefiles: build subdirs (Thanks Kacper)
2011-07-25 00:31:35 +02:00
fdd098b010
secure strscpy by replacing with strncpy
2011-07-23 22:22:36 +02:00
3749ed2fbe
Makefile: respect and use LIBS (Thanks Kacper)
2011-07-13 13:28:31 +02:00
93f906308d
makefiles: respect and use the CPPFLAGS variable (Thanks Kacper)
...
See also: http://stackoverflow.com/questions/2754966/cflags-vs-cppflags
2011-07-13 13:25:15 +02:00
307a036d5c
i3-msg, i3-input: get the I3_SOCKET_PATH atoms if socket path was not specified
2011-03-19 21:23:55 +01:00
cd0b7282e0
i3-input: remove dependency on xcb-event
2011-03-18 17:32:37 +01:00
7b01bc5eb7
Bugfix: use the global root variable, don’t get the first one (Thanks quaec)
...
The case of an X11 server having multiple displays is handled correctly by the
code in src/mainx.c. However, due to some functions not being correctly
refactored and still getting the first screen (and also the first root window)
from the XCB connection, i3 was operating on the wrong root window.
2011-01-28 00:41:53 +01:00
4caf85aa0b
Use I3SOCK-environment-variable
2011-01-12 10:15:48 +01:00
cd2ee61ee8
fix some memory leaks when user passes command line arguments twice (Thanks Tiago)
2011-01-12 10:12:24 +01:00
3d274cf2f9
Add font-option to i3-input
2011-01-02 12:22:39 +01:00
85730d6892
Fix numlock state
...
Apparantly, after activating numlock once, the numlock modifier
stays turned on (use xev(1) to verify). So, to resolve useful
keysyms, we remove the numlock flag from the event state. What
currently does not work is actually using your keypad.
2010-03-24 03:28:38 +01:00
Michael Stapelberg