Al_

The 'foot' field does in my opinion not allow the behaviour possible with 'post': 'data' ends with a space; the required bahaviour is a following pulse space pulse (and a long gap until the next IR key) As per http://www.lirc.org/html/lircd.conf.html, 'data' is only followed (if we cannot use 'post' and 'post_data') by ptrail (only a pulse), foot (pulse space) and gap (only a space) => pulse pulse space space. I.e., there is no option for a space between two pulses.

Excellent idea to check the publicly available remotes for use of pre and post. I downloaded today a snapshot from https://sourceforge.net/p/lirc-remotes/code/ci/master/tree/remotes/ , then run the following two grep commands to search for pre and post with a pulse length >0 (in the square brackets is a space and a literal tab): grep -A 5 -B 5 --recursive --extended-regexp --regexp='pre[ ]+[0-9][1-9]' ./ grep -A 5 -B 5 --recursive --extended-regexp --regexp='post[ ]+[0-9][1-9]' ./ There is no output...

Two .conf files to further clarify the usecase (see first paragraph of the original bug report). zehnderheating.conf does not send the 'post' pulse and space. zehnderheatingworkaround.conf is a workaround (that is possible as the trailing pulse happens to have the same duration as data pulses).

Hi See my previously reported issue with BLOB that do not properly load (initial...

Hi Chris Thanks for looking into this issue. The table definition is identical on...

bump Has anyone sync'ed BLOB from sqlite to sqlite?

Hi A sqlite database on android is loaded (initial load) from a sqlite master database...

Thanks! Now I found them. Will try soon.