This page last changed on Feb 27, 2014 by pz1.

A while ago I received an email about Pro-server maintenance on the 27th. Does that mean that this new Pro version will be released? If so does that version include the import of previously exported files?

The reason I am asking is that I have a rather tedious trivial editing task for the new RaZ-OR module. If I could have the import facility tomorrow, I rather postpone this work till tomorrow...

1.0.12 will indeed be released tomorrow, but does not include the export/import functionality (that still has some issues that require fixing before a release)

Posted by ebariaux at Feb 27, 2014 11:44

Thanks for the update.

Posted by pz1 at Feb 27, 2014 12:10

Does it contain the UDPListener update (passing regex group match)?

Posted by aktur at Feb 27, 2014 14:38

Do you know the issue number ? I see ORCJAVA-292 and 392 that talk about UDPListener

Anyway, no change on UDP in Pro 1.0.12

Posted by ebariaux at Feb 28, 2014 11:52

Yes, thats the one. Here follow one tip which I'm using to solve the problem which returning of timestamp was introduced in the first place.

This is done because IRtrans (that is where I use it for) is always sending the remote name and the button name. This means the received sensor value is always the same and since "old" value and "new" value are the same, the rules will not trigger when I press the same remote button a second time.

I was facing similar problem when trying to bind functions to double click of EnOcean buttons. In fact the solution is quite simple, just follow the template in a rule which should react on multiply clicks:

rule "button click"
salience -100
  $b: Event(source=="xyz")
  // do whatever you want with the click
  retract($b); // This allows for consecutive clicks to trigger this rule again
Posted by aktur at Feb 28, 2014 12:27

What has changed is in

Posted by pz1 at Feb 28, 2014 19:32

When can we expect it? ORCJAVA-292 has no activity since its creation over a year ago, ORCJAVA-392 has last been touched in August 2013. What else is in the pipeline for the next Pro version? Find it hard to get from Jira.

Posted by pz1 at Mar 08, 2014 12:49

Will discuss with team.

In JIRA, if you select a project, then a version, you see all issues assigned to that version.
So Controller, Pro 1.0.13 will give you issues scheduled for next Pro release of controller.

Note that issues can still be postponed or other issues prioritized before the release.

Posted by ebariaux at Mar 10, 2014 09:15
  • I know that part of the Jira. My confusion is with the relation between Pro 1.x.y versions and the 2.x.y versions.
  • What I miss is that bugs reported on the forum, and community developments do not always seem to make it to the Jira. My concern is that volunteers may be put off by the lack of clarity on the next steps for their contribution.
Posted by pz1 at Mar 10, 2014 09:34
Document generated by Confluence on Jun 05, 2016 09:38