14
I Use This!
Very Low Activity

News

Analyzed 28 days ago. based on code collected 4 months ago.
Posted 17 days ago by jwoi...@just42.net
dbus_util: import DBusQtMainLoop from dbus.mainloop.pyqt5 if dbus.mainloop.qt fails. While "dbus.mainloop.qt" appears to have been present in earlier versions of the PyQt?5 dbus modules for compatibility reasons, it seems it has been removed in ... [More] recent versions. Therefore if use of "dbus.mainloop.qt" fails, try using "dbus.mainloop.pyqt5" instead. This issue was noticed by Xavier Forestier and reported (with the suggested fix) via the ffado-devel mailing list on 6 June 2017. [Less]
Posted 17 days ago by jwoi...@just42.net
ffado-mixer: update manpage with information about the "-b" option. Commit r2670 added the "-b" option to ffado-mixer but the manpage was overlooked. This commit adds documentation about the "-b" option to the ffado-mixer manpage.
Posted 17 days ago by jwoi...@just42.net
mackieonyx: fix mixer module name inconsistency. The name of the python module implementing the Mackie Onyx mixer ("mackie_onyxmixer") was inconsistent with the class name as defined in the "configuration" file ("MackieOnyx?"). The class as ... [More] defined in "mackie_onyxmixer" ("MackieOnyx?") was fine though. To avoid causing unnecessary churn in existing "configuration" files, the mixer module was renamed to "mackieonyx", thus matching what is expected in the "configuration" file definition. This name mismatch was spotted by Xavier Forestier, who implemented a slightly different fix in his November 2016 patch set. [Less]
Posted 20 days ago by jwoi...@just42.net
ffado_mixer: use graphical icon instead of name for mixer pane if available. From Xavier Forestier's November 2016 patchset. In amongst the Qt5 changes was this code to utilise a device-specific graphical image instead of the textual device model ... [More] name in the global mixer pane. The only change from Xavier's patch is the omission of a statement to set the nickname placeholder text to the name of the device. The nickname field is present to support a particular feature of some interfaces, so it shouldn't really be repurposed like this. Otherwise there is a high likelihood of it introducing confusion when used with devices which support the nickname feature. FFADO does not currently ship with any device graphics. Contributions are welcome but care will be needed to ensure that copyrighted images from vendors are not used. The use of official images could give an incorrect impression that ffado-mixer is officially sanctioned by the vendors which is not generally the case. [Less]
Posted 20 days ago by jwoi...@just42.net
ffado-mixer: add device mixers to "View" menu. Xavier Forestier's November 2016 patchset included code which added an entry for each active device's mixer to the "View" menu. For users with a number of different devices this may prove useful. ... [More] This commits Xavier's original patch was with some minor changes to ensure the guid key is resolvable by setTabVisible() under PyQt?4. It has not been tested under PyQt?5. [Less]
Posted 20 days ago by jwoi...@just42.net
ffado_mixer: add a "Themes" submenu to the "View" menu. Xavier Forestier's November 2016 patchset included code to add themes under the "Help" menu which could be selected by the user. The code to do this is relatively simple so there seems ... [More] little reason to hold it back. The only change compared to the submitted patch is to move the themes to a submenu of the "View" menu since conceptually this is a better place than the top of the "Help" menu. [Less]
Posted 20 days ago by jwoi...@just42.net
matrixmixer.py: attempt to deal with UTF8 string changes in python3. PyQt?5 under python3 does not implement QString and instead relies on the native python UTF string type. Attempt to deal with this when drawing mixer elements which make use of ... [More] UTF characters. This has not yet been tested under python3 due to the author not having access to a system with python3, so testing may yet prove that the approach taken in this commit is insufficient. This commit is based on the suggestion from Xavier Forestier in his patch set from November 2016 submitted via the ffado-devel mailing list. [Less]
Posted 20 days ago by jwoi...@just42.net
A first pass at optionally supporting PyQt?5 in the build system. This is an initial implementation of changes in the build system to support the use of PyQt?5 when building ffado-mixer. They are based on the patch set submitted to ffado-devel by ... [More] Xavier Forestier in November 2016. However, rather than removing PyQt?4 support, the idea is that either PyQt?4 or PyQt?5 can be used. This patch has been tested on a machine with only PyQt?4 installed. Testing with only PyQt?5 is yet to be done (the author presently does not have access to such a system). It is not known how well this patch will work on a machine with both PyQt?4 and PyQt?5 installed. r2694 assumes that PyQt?4 will be used in this situation on the basis that it has had the most testing, but it's unclear whether the build system will select pyuic4 over pyuic5 in this case. Further testing will be required, and adjustments will be made if problems are found. [Less]
Posted 20 days ago by jwoi...@just42.net
ffado_diag_helpers.py: get_version_first_line(): print "Not found" if the command is available. Previously a shell error message would be shown which may be a little misleading in some situations.
Posted 21 days ago by jwoi...@just42.net
import_pyqt.py: make licence format consistent with the rest of FFADO.