summaryrefslogtreecommitdiffstats
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
...
* | Calculate timeout only when recording startsMatthias Vogelgesang2012-08-071-1/+1
| | | | | | | | | | Reading register values is not really fast, so we keep the last exposure time when starting the acquisition.
* | Benchmark: add asynchronous testMatthias Vogelgesang2012-08-071-37/+96
| |
* | Benchmark: Implement message loggingMatthias Vogelgesang2012-08-071-7/+53
| | | | | | | | | | Because the UFO camera sometimes errors when grabbing frames, we redirect error messages to the log file error.log.
* | Update benchmark toolMatthias Vogelgesang2012-08-072-61/+112
|/ | | | | | The tool measures the bandwidth performance of a supplied camera. It outputs the results in standard space separated format that can be read with Numpy's loadtxt function.
* Install glade file into prefix/share/libucaMatthias Vogelgesang2012-07-184-15/+17
|
* Remove scale widgetMatthias Vogelgesang2012-07-122-59/+5
|
* Scale automatically and fix some warnings with UFOMatthias Vogelgesang2012-07-112-27/+27
|
* Remove unnecessary functionMatthias Vogelgesang2012-07-111-35/+7
|
* Fix ui issuesMatthias Vogelgesang2012-07-092-2/+2
|
* Backport combo box in property rendererMatthias Vogelgesang2012-07-091-2/+97
|
* Pass camera type from command line to grabMatthias Vogelgesang2012-07-061-19/+28
|
* Remove unused variableMatthias Vogelgesang2012-07-061-3/+0
|
* Remove unnecessary codeMatthias Vogelgesang2012-07-041-75/+0
|
* Add property tree viewMatthias Vogelgesang2012-07-047-66/+740
| | | | | | | | | The standard tree view widget is not capable of setting individual cell renderers per row. Thus I made one with a custom cell renderer that uses an appropriate cell renderer depending of the property type. I developed this independently and put it up on Github at https://github.com/matze/EggPropertyTreeView.
* Fix LU-16: Add cooling point propsMatthias Vogelgesang2012-07-031-0/+6
| | | | | Added "cooling-point-min", "cooling-point-max" and "cooling-point-default" to query the valid range of "cooling-point".
* Use dogmatic Gtk+ way of styling treeview columnsMatthias Vogelgesang2012-07-022-9/+10
|
* Fix LU-15: Broken ROI imageMatthias Vogelgesang2012-06-291-4/+9
| | | | | | | | This fix contains two changes: 1. We check that passed ROI requests are multiples of possible ROI steps as provided by the camera. If this is not the case, the request is ignored and a warning issued. 2. We added two new base properties ROI_WIDTH_MULTIPLIER and ROI_HEIGHT_MULTIPLIER that expose this information to client programs.
* Re-implement asynchronous data acquisitionMatthias Vogelgesang2012-06-203-53/+78
|
* Fix LU-4Matthias Vogelgesang2012-06-141-7/+17
| | | | The larger sensor area can now be used as a ROI.
* Use roi-x0 and roi-y0Matthias Vogelgesang2012-06-121-4/+4
|
* Allow only possible pixel rates when settingMatthias Vogelgesang2012-06-011-3/+4
|
* Set different grabbing parametersMatthias Vogelgesang2012-05-291-10/+29
|
* Fix exposure and delay timeMatthias Vogelgesang2012-05-291-1/+4
|
* Print more meaningful error messageMatthias Vogelgesang2012-05-101-1/+1
|
* Drop -gobject suffixMatthias Vogelgesang2012-04-201-28/+16
|
* Output error when stoppingMatthias Vogelgesang2012-04-201-4/+7
|
* Leave properties for laterMatthias Vogelgesang2012-04-201-1/+1
|
* Add Photon FocusMatthias Vogelgesang2012-04-191-2/+6
|
* Export base properties and string arrayMatthias Vogelgesang2012-04-192-7/+9
| | | | | | | The benefits are two-fold: Camera implementations "know" which base properties exist without looking into the implementation source. Moreover, they can re-use the property strings rather than stating them over and over again. These change should reduce potential c&p errors.
* Require Gtk+ 2.22Matthias Vogelgesang2012-04-171-1/+1
| | | | | The control application will not be built on the Hudson server and thus not break the build.
* More meaningful async testMatthias Vogelgesang2012-04-171-4/+9
| | | | | Before we just checked that the callback was called. Now we check that it is called as often as expected.
* Fix property settingMatthias Vogelgesang2012-04-171-2/+2
|
* This test is unnecessaryMatthias Vogelgesang2012-04-162-23/+0
|
* Implement property editingMatthias Vogelgesang2012-04-162-62/+168
|
* Port control application to libuca 0.6Matthias Vogelgesang2012-04-163-256/+218
|
* Fix multiple recordingsMatthias Vogelgesang2012-04-131-4/+8
|
* Start and stop recording in a loopMatthias Vogelgesang2012-04-121-16/+23
|
* Add test to measure lib overheadMatthias Vogelgesang2012-04-022-0/+150
|
* Merge patch from Volker KaiserMatthias Vogelgesang2012-03-211-3/+3
|
* Fix mock cameraMatthias Vogelgesang2012-03-081-1/+2
| | | | All unit tests pass again
* Quick fix for openSUSE 11.3 with GLib 2.24Matthias Vogelgesang2012-03-081-3/+3
|
* Implement single frame grabbingMatthias Vogelgesang2012-03-063-57/+57
|
* pco: Implement mandatory propertiesMatthias Vogelgesang2012-03-061-3/+8
|
* Add test facility that uniformly tests all camerasMatthias Vogelgesang2012-03-052-0/+201
|
* Add factory method to create new camerasMatthias Vogelgesang2012-03-052-12/+13
|
* Complete async xfer infrastructureMatthias Vogelgesang2012-03-051-3/+32
|
* Fix error handlingMatthias Vogelgesang2012-03-051-0/+1
| | | | Obviously, unit tests pay off.
* Use property notification instead of signalMatthias Vogelgesang2012-03-052-14/+48
| | | | | | | Up to this point we used a custom signal to notify about starting and stopping recording of data. However, such signals come (almost) for free for each property. This way, you can query "is-recording" but also be notified when "is-recording" was changed by the camera itself.
* Add mock testMatthias Vogelgesang2012-03-051-0/+98
|
* Add start/stop signalMatthias Vogelgesang2012-03-031-6/+6
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-11 11:02:09 +0000