IRC logs of #tryton for Friday, 2017-04-14 #tryton log beginning Fri Apr 14 00:00:01 CEST 2017
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton00:59
-!- VaticanCameos(~VaticanCa@ has joined #tryton03:52
-!- thaneor1(~ldlc6@ has joined #tryton03:56
-!- csotelo(~csotelo@2001:1388:49c5:43b8:d3e2:751c:85f2:faf) has joined #tryton04:53
-!- VaticanCameos(~VaticanCa@ has joined #tryton05:17
-!- dj_xatra(~dj_xatra@ has joined #tryton08:07
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton08:51
-!- mrichez( has joined #tryton08:52
-!- VaticanCameos(~VaticanCa@ has joined #tryton09:18
-!- nicoe( has joined #tryton09:57
cedkpokoli: what about issue6420?11:28
-!- Telesight( has joined #tryton12:40
-!- EdbO(8911351a@gateway/web/freenode/ip. has joined #tryton14:00
EdbOGot a strange thing with buttons14:01
EdbOWhen I create a button rule with multiple clicks14:01
EdbOAnd use that button in a workflow14:01
EdbOI get an empty array instead of the the item14:02
EdbOWhen I do the same with a "normal" button, it works like expected14:02
EdbOE.g. with a "normal" button I got [Pool().get('account.invoice')(4)], with multiple clicks I get []14:04
cedkEdbO: if the record did not reach the right number of clicks it is filtered14:25
EdbOcedk: I configurered the button to be clicked twice, after the second click I still get an empty array14:40
EdbOcedk: Also after the first click, the code got executed.14:40
cedkEdbO: I guess you did not configured correctly14:42
EdbOcedk: I configured it correctly. A few weeks back I configured the button
cedkEdbO: if the code is executed after the first click than why do you click a second time?14:48
cedkEdbO: after a succeful click the counter is reset14:49
cedkEdbO: also have you applied
EdbOcedk: Because the transistion is done after the second click.14:57
EdbOcedk: I already applied
cedkEdbO: I do not understand14:59
cedkEdbO: what transition are you talking?14:59
EdbOcedk: Transision of the state from "draft" to "confirmed"15:02
cedkEdbO: I really do not understand at all your stories15:03
EdbOcedk: No problem. I wil figure it out myself and maybe report a bug15:04
-!- trilliji( has joined #tryton15:06
cedkACTION last time I try to help EdbO15:07
-!- thaneor(~ldlc6@ has joined #tryton15:59
-!- Telesight( has joined #tryton16:27
-!- EdbO(5065932f@gateway/web/freenode/ip. has joined #tryton17:21
EdbOcedk: you don't have to answer, but what's wrong with figuring out myself a.k.a digging deeper into tryton how it works? To me it's better that you spend your quality time on doing the right stuff instead trying to understand me. We could spend a lot of time talking about the problem and than conclude that I missed a bit (which I now have discovered myself and learned a bit extra about how tryton works). Maybe I had to say it a bit diff17:31
-!- rpit(~rpit@2a02:908:e672:7480:56ee:75ff:fe0d:d3c7) has joined #tryton18:16
-!- prakashpandey(~prakashpa@ has joined #tryton18:51
prakashpandey:cedk what are your thoughts on implementing read nested read on o2m or m2m fields. Something like[id], ['addresses.rec_name']) = [{'': ['address1 name', 'address2 name']}]18:53
cedkprakashpandey: I do not think it makes sense or even be practicable18:58
cedkprakashpandey: because there will be no way to know the id of the record read18:58
prakashpandey:cedk and because read doesn't respect the order. Makes sense19:02
-!- rpit(~rpit@2a02:908:e672:7480:56ee:75ff:fe0d:d3c7) has joined #tryton19:04
-!- robink(~quassel@unaffilated/robink) has joined #tryton20:59

Generated by 2.11.0 by Marius Gedminas - find it at!