IDempiere/FullMeeting20140521 - Revision history

CarlosRuiz: drop JIRA notifications from log

2014-05-21T22:36:40Z

drop JIRA notifications from log

CarlosRuiz: full meeting

2014-05-21T22:36:02Z

full meeting

New page

⇐
[[IDempiere|Table of Contents]] |
[[IDempiere/Full Meeting Minutes|Full Meeting Minutes]] |
Full Meeting 2014-05-21


'''''CarlosRuiz''''': Good morning 
'''''nmicoud''''': Bonjour 
'''''tbayen''''': Daarestiet! 
'''''nmicoud''''': any idea for the last comment on https://idempiere.atlassian.net/browse/IDEMPIERE-1899 ? 
'''''CarlosRuiz''''': nmicoud, I would like to integrate it as is if you don't mind - and see if somebody else can improve it with your idea 
'''''nmicoud''''': yes, no problem 
'''''tbayen''''': I do not understand your last comment. I see on your screenshot that the images are broken. I do not understand when are they shown and when not? 
'''''nmicoud''''': they are not shown when you write the email dialog, but shown when you read the received email 
'''''tbayen''''': ah, ok. I understand. 
'''''Not-f074''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to development [+3/-0/±4] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-f074''''': [iDempiere] globalqss 05d5a3c - IDEMPIERE-1899 EMail : Implement default mail text and allow images within message / based on patch and idea from Nicolas Micoud (nmicoud) 
'''''tbayen''''': If noone has big problems to discuss I want to ask what do you think about https://idempiere.atlassian.net/browse/IDEMPIERE-1955 ? 
'''''tbayen''''': This will "solve" some kinds of problems for non-accounting installations and be a help for bad maintained translations. 
'''''CarlosRuiz''''': yes - I have a file like that for starting all installations 
'''''CarlosRuiz''''': in some installations I just install that file and then via SQL inactivate all the created accounts 
'''''tbayen''''': If you inactivate the default accounts you can not close any document, can't you?!? 
'''''CarlosRuiz''''': in my file I added a summary node called "Not Configured Default Accounts" and grouped accounts there 
'''''CarlosRuiz''''': accounting is independent process - you can do everything except posting 
'''''tbayen''''': What do you think about using it automatic if a user does not set a coa file? 
'''''CarlosRuiz''''': already discussed at https://idempiere.atlassian.net/browse/IDEMPIERE-1685 
'''''tbayen''''': I found the very same just in this second. :-) 
'''''CarlosRuiz''''': what about a flag "no initial accounting" (comment -> you can activate it later) 
'''''tbayen''''': What exactly happens if the account is inactivated and you close a document? Will it be closed but not posted? Without an error message about that fact? 
'''''CarlosRuiz''''': accounting is independent - doesn't affect the workflows 
'''''tbayen''''': The thinking behind this coa is to have the whole "coa thing" out of the way. If we think this to the end then inactivating sounds like the right idea. But on the other hand you can use this as an the "smalles possible coa file" and use it for real accounting. 
'''''aguerra_''''': Hi everybody!!!! 
'''''CarlosRuiz''''': tbayen, I think they are different problems -> no accounting <> minimum accounting 
'''''CarlosRuiz''''': Hi aguerra_ 
'''''CarlosRuiz''''': if user will use accounting (even minimum) then I think is fine he must know what he's doing and choose a proper CoA 
'''''tbayen''''': CarlosRuiz, yes. This leads to the need to document it. :-) All ways lead to the old same story... 
'''''CarlosRuiz''''': if user is not going to use accounting then sounds ok to have a flag and create automatically those accounts and even inactivate them 
'''''CarlosRuiz''''': it is documented 
'''''CarlosRuiz''''': there are several pages documenting client creation - this is one of those http://www.adempiere.com/Initial_Client_Setup_Process 
'''''hieplq''''': or add a combobox with three option (blank:must choose COA file, no account: inactive account, min account: for default file) 
'''''tbayen''''': We talked about coa files in the german community. My feeing is that this area needs much more documentation. Or it needs a good way to get it out of the way for those who do not care. 
'''''CarlosRuiz''''': writing a draft here ... 
'''''Edwin_Ang''''': Hi everyone 
'''''CarlosRuiz''''': Hi Edwin_Ang 
'''''Edwin_Ang''''': Hi Carlos 
'''''hieplq''''': CarlosRuiz, please help in this ticket. https://idempiere.atlassian.net/browse/IDEMPIERE-1957 it's ok to add to core? 
'''''hieplq''''': i need know to continue improve IDEMPIERE-1334 
'''''CarlosRuiz''''': how's the usage of 1957? programatically? 
'''''hieplq''''': I can add more info (tooltip, help, desc) to infoProcess table, after that. call new function when user focus a process button 
'''''hieplq''''': => tooltip panel is update 
'''''CarlosRuiz''''': ah good 
'''''hieplq''''': IDEMPIERE-1334 is almost finish, you can quick review and give me advice 
'''''CarlosRuiz''''': ok - will try to check 1334 later .. let me finish the draft for CoA 
'''''CarlosRuiz''''': tbayen, just noticed you can have a CoA file with just one account :-) 
'''''tbayen''''': I expected errors if accounts are missing. 
'''''tbayen''''': Which is the magic one?!? DEFAULT? 
'''''CarlosRuiz''''': look here http://pastebin.com/x6U9c7cd 
'''''CarlosRuiz''''': tbayen, did you receive my pastebin link? my wifi died 
'''''tbayen''''': Yes, I received it. 
'''''CarlosRuiz''''': ok - I'm ready to publish the draft 
'''''CarlosRuiz''''': not a draft - I already tested it - but I'll appreciate your tests 
'''''tbayen''''': I think about what is better. Your solution creates only one account. My solution can be easier transfered into a fully functional accounting later. I wonder if one or the other is better or if they are for different usecases. 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1685 Attachment set to "IDEMPIERE-1685.zip" 
'''''Not-f074''''': [IDEMPIERE] Uploading suggested patch for peer review 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1685 
'''''CarlosRuiz''''': yes - I think the "one account" is useful just if you're not going to use accounts 
'''''CarlosRuiz''''': just found curious that option is available 
'''''CarlosRuiz''''': ok - I uploaded the patch 
'''''CarlosRuiz''''': it creates three new parameters on the Initial Client Setup process 
'''''CarlosRuiz''''': Use Activity Dimension, Use Default CoA, Inactivate Defaults 
'''''CarlosRuiz''''': if you set Use Default CoA - then CoAFile parameter is hidden 
'''''CarlosRuiz''''': also added your CoA file with one summary account and created the logic to summarize it there 
'''''CarlosRuiz''''': I think it will work in a server installation out of the box 
'''''CarlosRuiz''''': but to test in eclipse you need to set a sysconfig key 
'''''CarlosRuiz''''': DEFAULT_COA_PATH 
'''''CarlosRuiz''''': with the path pointing to your test file 
'''''CarlosRuiz''''': in my case was pointing to 
'''''CarlosRuiz''''': /home/carlos/hgAdempiere/localosgi/org.adempiere.server-feature/data/import/AccountingDefaultsOnly.csv 
'''''tbayen''''': ok. I will test if this evening. 
'''''tbayen''''': For me it is not sure why you need a sysconfig key. Can't you get it out of the classpath? 
'''''CarlosRuiz''''': the default location of the default file is 
'''''CarlosRuiz''''': {idempiere_home}/data/import/AccountingDefaultsOnly.csv 
'''''CarlosRuiz''''': that's ok on server 
'''''CarlosRuiz''''': but not ok within eclipse 
'''''CarlosRuiz''''': but also the sysconfig key is intentional - it allows you to set a different default file for your installation (i.e in spanish for me) 
'''''tbayen''''': ok 
'''''tbayen''''': My thought were that someone who cares about language and such would load an dedicated coa file and not use defaults. But to have this possibility can not be bad. 
'''''CarlosRuiz''''': or maybe somebody could like the "just one account" approach - and is just change the sysconfig 
'''''tbayen''''': Yes - it gives more possibilities for the implementor. 
'''''norbertbede''''': hi all 
'''''CarlosRuiz''''': Hi norbertbede 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1955 status set to "Resolved" -assignee set to "Thomas Bayen" -resolution set to "Fixed" 
'''''Not-f074''''': [IDEMPIERE] taking the idea from here to resolve IDEMPIERE-1685 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1955 
'''''Not-f074''''': [IDEMPIERE] red1 updated IDEMPIERE-1813 
'''''Not-f074''''': [IDEMPIERE] Budget.pdf version 0.5 on OutputMessage handling http://sourceforge.net/projects/red1/upload/p2/Budget/ 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1813 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1685 status set to "Peer Review Queue" 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1685 
'''''CarlosRuiz''''': ah bitbucket changed layout 
'''''CarlosRuiz''''': https://bitbucket.org/idempiere/idempiere/ 
'''''CarlosRuiz''''': "There isn't a README yet 
'''''CarlosRuiz''''': Create one and tell people where to start and how to contribute" 
'''''CarlosRuiz''''': any volunteer to create a good README there? 
'''''Not-f074''''': [IDEMPIERE] norbert.bede updated IDEMPIERE-1334 
'''''Not-f074''''': [IDEMPIERE] tested, looks me ready to commit from the side of concept. anyway code review from [~carlosruiz_globalqss] required. norbert 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1334 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1334 Tested By set to "Norbert Bede" 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1334 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1960 status set to "Resolved" -resolution set to "Fixed" 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1960 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss created IDEMPIERE-1961 Double click on checkbox applies display logic just once 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1961 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1961 Attachment set to "jira-capture-screenshot-20140521-111258-595.png" 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1961 
'''''Not-f074''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to release-2.0 [+0/-0/±7] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-f074''''': [iDempiere] hengsin 296bd32 - IDEMPIERE-1960 InfoWindow: Can't set column with context variable as selection column. 
'''''norbertbede''''': @carlos is it right time to review this issue http://idempiere.atlassian.net/browse/IDEMPIERE-1334 Run one or more processes from Info Window ? 
'''''CarlosRuiz''''': I'm on it - hieplq asked me first to review 1957 which is dependent 
'''''norbertbede''''': we want to finish this if possible with hiep. continue other our features 
'''''norbertbede''''': ah ok. 
'''''norbertbede''''': i joined to chate late…thanks 
'''''Not-f074''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to development [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-f074''''': [iDempiere] hieplq dc9f607 - IDEMPIERE-1957:add ability to make tooltip for any control not only gridField 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1957 status set to "Resolved" -assignee set to "hieplq" -resolution set to "Fixed" 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1957 
'''''CarlosRuiz''''': hieplq, still here? 
'''''hieplq''''': yes. i'm here 
'''''CarlosRuiz''''': there are three files attached to 1334 
'''''CarlosRuiz''''': is the last enough? or I must apply several? 
'''''hieplq''''': just last 
'''''hieplq''''': and .zip is packin data 
'''''CarlosRuiz''''': no migration script with official IDs? 
'''''hieplq''''': i will make it after you review code. 
'''''CarlosRuiz''''': cannot merge either - some files rejected 
'''''CarlosRuiz''''': org.adempiere.ui.zk/WEB-INF/src/org/adempiere/webui/apps/ProcessModalDialog.java.rej 
'''''CarlosRuiz''''': org.adempiere.ui.zk/theme/default/css/fragment/form.css.dsp.rej 
'''''CarlosRuiz''''': form.css.dsp doesn't exist 
'''''hieplq''''': i can merge it with last zk7 brank. please wait me test with dev brank 
'''''CarlosRuiz''''': ah - I'm not using zk7 
'''''CarlosRuiz''''': zk7 has not been merged with latest changes on process dialog 
'''''hieplq''''': ok. i will fix now. please wait me 
'''''tbayen''''': I see that the table c_bp_relation has its own window. Why is it not a register in the bpartner window? Is it just a menu design decision or is there a technical reason I do not see? 
'''''CarlosRuiz''''': don't know what JJ was thinking at that time :-) but usually you put a window in its own menu when you want easier role control 
'''''CarlosRuiz''''': in this case would be something like - if you want a role able to configure relations, but not able to configure partners 
'''''Not-f074''''': [IDEMPIERE] hieplq updated IDEMPIERE-1334 Attachment set to "IDEMPIERE-1334-remain-select-after-refresh_dev_branch.patch" 
'''''Not-f074''''': [IDEMPIERE] update patch for dev branch 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1334 
'''''tbayen''''': ok. thanks 
'''''hieplq''''': CarlosRuiz, I update patch. please help me review. i will retest it 
'''''Not-f074''''': [IDEMPIERE] hieplq updated IDEMPIERE-1916 status set to "Open" 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1916 
'''''Not-f074''''': [IDEMPIERE] hieplq updated IDEMPIERE-1916 status set to "Closed" -resolution set to "Won't Fix" 
'''''Not-f074''''': [IDEMPIERE] make it as plug-in code commit at https://bitbucket.org/hieplq/hsv-plugin/commits/ebcf7dccad94ca2995534b24796c7cae86700373 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1916 
'''''CarlosRuiz''''': ok 
'''''Not-f074''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to release-2.0 [+2/-0/±13] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-f074''''': [iDempiere] hengsin df38654 - IDEMPIERE-1953 Performance problem of BOM* functions ( Part of Ticket 1004000 ). 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1953 
'''''Not-f074''''': [IDEMPIERE] Adding some documentation about commit http://bitbucket.org/idempiere/idempiere/commits/df38654 POSTGRESQL has three types of functions: http://www.postgresql.org/docs/9.3/static/sql-createfunction.html volatile (the default) stable (the return for same parameter is the same within a trx) immutable (the return is always the same) so, changing the postgresql functions to stable speed up queries because the return value is cached ORACLE: ht 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1953 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1953 labels set to "+Patch" 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1953 
'''''CarlosRuiz''''': hieplq? 
'''''hieplq''''': i'm here 
'''''CarlosRuiz''''': would be possible to create a column on infoprocess - instead of the sysconfig keys 
'''''CarlosRuiz''''': with the three options that you put there - button, droplist, dialog 
'''''CarlosRuiz''''': and you paint buttons according to each definition 
'''''hieplq''''': yes. it can 
'''''CarlosRuiz''''': and you can combine different type of buttons on the same window? or too complex? 
'''''hieplq''''': "combine different type of buttons on the same window" you can more detail? 
'''''CarlosRuiz''''': so, I think you could have direct buttons - other less used in droplist - and others even less used on a dialog 
'''''hieplq''''': ah. i know 
'''''CarlosRuiz''''': if you add this column replacing the sysconfig - i.e. AD_InfoColumn.ButtonType 
'''''CarlosRuiz''''': then you can define where you want the button - and possibly you have the three types 
'''''hieplq''''': yes. it can with no complex 
'''''hieplq''''': 1. in infoWindow add column layoutStyle, in each infoProcess add column groupLayoutStyle. 
'''''CarlosRuiz''''': column layout? 
'''''CarlosRuiz''''': ah no - the first is not needed 
'''''hieplq''''': when all infoProcess have groupLayoutStyle = null => all button in layout of infoWindow 
'''''CarlosRuiz''''': I think just the second 
'''''CarlosRuiz''''': with a default of your preference 
'''''hieplq''''': 1 is for implement like add all buton in a style 
'''''hieplq''''': he not need define in each infoprocess row 
'''''CarlosRuiz''''': no need for that if you can do it in detail - and the volume is not that high 
'''''hieplq''''': ok. i will try with preference 
'''''Not-f074''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to release-2.0 [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-f074''''': [iDempiere] hengsin 1fb73c3 - 1004000 Performance issue with product info form. Minor fix for checking of empty order by clause. 
'''''CarlosRuiz''''': preference? 
'''''hieplq''''': "with a default of your preference" i think you mean use preference to set default for all button in a info window 
'''''CarlosRuiz''''': no 
'''''CarlosRuiz''''': I mean just set a default for the column - the one you like more 
'''''CarlosRuiz''''': or in the code just check - if ButtonLayout is empty then assume your preferred 
'''''hieplq''''': huh. it's ok with me. but add a column to infoWindow is easy for other config. 
'''''CarlosRuiz''''': just keep it simple 
'''''hieplq''''': ok. no problem. will make that. 
'''''Not-f074''''': [iDempiere] CarlosRuiz_globalqss pushed 2 commits to release-2.0 [+0/-0/±3] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-f074''''': [iDempiere] hengsin 1ba3fc0 - 1003754 Landed cost issue -- related to IDEMPIERE-1285. Fix landed cost allocation to product not working. 
'''''Not-f074''''': [iDempiere] hengsin 35c0598 - 1003754 Landed cost issue -- related to IDEMPIERE-1285. Fix rounding issue with current product cost for average costing. 
'''''Not-f074''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to release-2.0 [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-f074''''': [iDempiere] elainetan 73ebe12 - IDEMPIERE-1958 Incorrect table start position in Table Element report layout code 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1958 status set to "Resolved" -resolution set to "Fixed" 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1958 
'''''Not-f074''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to development [+2/-0/±4] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-f074''''': [iDempiere] hengsin e2d5ea7 - Ticket #1004012 IDEMPIERE-1954 Implement MaxQueryRecords for AD_InfoWindow. 
'''''Not-f074''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-1954 status set to "Resolved" -assignee set to "Heng Sin Low" -resolution set to "Fixed" 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1954 
'''''CarlosRuiz''''': hieplq, just committed a change to InfoWindow and InfoPanel - so, please pull for your new patch 
'''''hieplq''''': ok. 
'''''Not-f074''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to development [+2/-0/±19] https://bitbucket.org/idempiere/idempiere/commits/ 
'''''Not-f074''''': [iDempiere] globalqss 03f832a - hg merge release-2.0 (merge release2 into development) 
'''''Not-f074''''': [IDEMPIERE] red1 updated IDEMPIERE-1813 
'''''Not-f074''''': [IDEMPIERE] Budget.pdf version 0.5 on OutputMessage handling http://sourceforge.net/projects/red1/files/p2/Budget/ 
'''''Not-f074''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-1813

@@ Line 16: / Line 16: @@
 '''''nmicoud''''': they are not shown when you write the email dialog, but shown when you read the received email<br>
 '''''tbayen''''': ah, ok. I understand.<br>
 '''''tbayen''''': If noone has big problems to discuss I want to ask what do you think about https://idempiere.atlassian.net/browse/IDEMPIERE-1955 ?<br>
 '''''tbayen''''': This will "solve" some kinds of problems for non-accounting installations and be a help for bad maintained translations.<br>
@@ Line 63: / Line 61: @@
 '''''CarlosRuiz''''': not a draft - I already tested it - but I'll appreciate your tests<br>
 '''''tbayen''''': I think about what is better. Your solution creates only one account. My solution can be easier transfered into a fully functional accounting later. I wonder if one or the other is better or if they are for different usecases.<br>
 '''''CarlosRuiz''''': yes - I think the "one account" is useful just if you're not going to use accounts<br>
 '''''CarlosRuiz''''': just found curious that option is available<br>
@@ Line 92: / Line 87: @@
 '''''norbertbede''''': hi all<br>
 '''''CarlosRuiz''''': Hi norbertbede <br>
 '''''CarlosRuiz''''': ah bitbucket changed layout<br>
 '''''CarlosRuiz''''': https://bitbucket.org/idempiere/idempiere/<br>
@@ Line 105: / Line 92: @@
 '''''CarlosRuiz''''': Create one and tell people where to start and how to contribute"<br>
 '''''CarlosRuiz''''': any volunteer to create a good README there?<br>
 '''''norbertbede''''': @carlos is it right time to review this issue http://idempiere.atlassian.net/browse/IDEMPIERE-1334 Run one or more processes from Info Window ?<br>
 '''''CarlosRuiz''''': I'm on it - hieplq asked me first to review 1957 which is dependent<br>
@@ Line 123: / Line 97: @@
 '''''norbertbede''''': ah ok.<br>
 '''''norbertbede''''': i joined to chate late…thanks<br>
 '''''CarlosRuiz''''': hieplq, still here?<br>
 '''''hieplq''''': yes. i'm here<br>
@@ Line 146: / Line 116: @@
 '''''CarlosRuiz''''': don't know what JJ was thinking at that time  :-)   but usually you put a window in its own menu when you want easier role control<br>
 '''''CarlosRuiz''''': in this case would be something like - if you want a role able to configure relations, but not able to configure partners<br>
 '''''tbayen''''': ok. thanks<br>
 '''''hieplq''''': CarlosRuiz, I update patch. please help me review. i will retest it<br>
 '''''CarlosRuiz''''': ok<br>
 '''''CarlosRuiz''''': hieplq?<br>
 '''''hieplq''''': i'm here<br>
@@ Line 187: / Line 142: @@
 '''''CarlosRuiz''''': no need for that if you can do it in detail - and the volume is not that high<br>
 '''''hieplq''''': ok. i will try with preference<br>
 '''''CarlosRuiz''''': preference?<br>
 '''''hieplq''''': "with a default of your preference" i think you mean use preference to set default for all button in a info window<br>
@@ Line 197: / Line 150: @@
 '''''CarlosRuiz''''': just keep it simple<br>
 '''''hieplq''''': ok. no problem. will make that.<br>
 '''''CarlosRuiz''''': hieplq, just committed a change to InfoWindow and InfoPanel - so, please pull for your new patch<br>
 '''''hieplq''''': ok.<br>