| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Create the EventLoop abstract class, add documentation for signal handling
|
| |/
|
|
| |
use Python .gitignore provided by GitHub
|
| |\
| |
| | |
Allow Screen class to set signal handlers using a function provided by the event loop
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
loop
The Screen class used to set signal handlers using the signal() function
from the signal standard library module. This commit changes this
behaviour so that the Screen class now uses a function provided by the active
event loop to set signal event handlers. This allows us to use GLib
specific signal handling functions when using the GLib event loop.
|
| |\ \
| | |
| | | |
Fix default screen size on raw display
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Python3 fix in graph example
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
fix: raw display should release file descriptors (issue #221)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
`raw_display.Screen.hook_event_loop` does not fill
`self._current_event_loop_handles` with handled file descriptors.
So, `raw_display.Screen.hook_event_loop` can not release then.
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | | |
Additional linebox functionality
|
| | | | | |
| | | | |
| | | | |
| | | | | |
layout
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Add title_align as a new keyword argument to construct a ListBox. It
allows justifying a ListBox to the left or right in addition to
centering it. This can be useful for constructing columns out of
ListBoxes.
* Implement borderless sides. If a ListBox is created with lines or
corners set to the empty string then do not create a border element
for them. This allows adjoining list boxes to share a single border,
or two ListBoxes to seamlessly merge into one another.
Fixes #211
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Typo fixes
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Correct error messages in Filler
|
| | | | | | | |
| | | | | | |
| | | | | | | |
The error message talks about conditions for `fixed bottom` argument to be valid, when the argument is set to `fixed top`. This doesn't seem right.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* WIP
* Metaclasses
* String literal fixes
* Remove 2to3 and make tests compatible with both Python 2 & 3
* Removed debug code.
* Added tests for ProgressBar
* Fixed examples.
* future division & font literals fix
* Cleaner fonts initialization.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Feature/listbox home end
|
| | |\ \ \ \ \ \ \ |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Pressing 'home' moves the focus to the first position, 'end' moves focus to the
last position.
|
| |\ \ \ \ \ \ \ \ \
| |_|_|_|_|/ / / /
|/| | | | | | | | |
Correct Edit documentation
|
| | | |_|/ / / / /
| |/| | | | | |
| | | | | | | | |
There were missing doc comments for a few basic properties, + the text about `edit_text` property being a read-only property was a lie.
|
| |\ \ \ \ \ \ \ \
| |_|/ / / / / /
|/| | | | | | | |
Emit postchange after text is updated
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Just like Edit() boxes, CheckBox and RadioButton need to have an event
emitted after the change has been commited. This allows us to modify
the state after it occurs. (If the event only fires before the state is
actually changed, the event handler cannot change the state because the
emitter will change it to what they were going to after the event
handler has finished.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The Edit widget in 1.3.0 has a "change" signal which fires before the
edit_text is updated. This means that change signal handlers cannot
update the edit_text; the text is updated by the signal emitter after
the change handler has finished running. To remedy this, in a backwards
compatible way, create a second signal, "postchange" which fires after
edit_text has been changed. "postchange" sends the widget's old text
value as a parameter so that change handlers can use the former value
if needed (for instance, to revert a change because the new_text was
invalid)
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Sometimes an Edit's change handler wants to edit the text that has just
been entered. For instance, if the handler does validation, it may want
to immediately highlight or prevent invalid entries from being shown.
This is not possible if the change signal is emitted before the internal
text data is updated as the update will overwrite anything that the
change handler performed. Emitting the change event after the update
has been performed allows for changes to be made.
Fixes #212
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
[RFC] New foreground setting "strikethrough"
|
| |/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
If you are unsure if your terminal supports this, try the following:
echo -e "\e[9mstrikethrough\e[0m"
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Fix typos
|
| | | |_|_|_|/ / /
| |/| | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Mention blink and italics attributes in manual.
|
| | | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
python 3 compatibility changes
|
| | |/ / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
this updates the syntax in many of the examples so that they run under
both python 2 and python 3.
|
