Le 22/11/2010 20:21, Wayne Stambaugh a écrit :
I'm not sure what m_oldRootName is for. I believe JP added that.
Perhaps he could shed some light this.
Wayne
I do not remember anything about this ...
Well, perhaps it could be removed.
--
Jean-Pierre CHARRAS
__
I'm not sure what m_oldRootName is for. I believe JP added that.
Perhaps he could shed some light this.
Wayne
On 11/22/2010 1:03 PM, Marco Mattila wrote:
> Ok, but what was the bug/issue that was fixed by introducing
> m_oldRootName? Before 2559 it was possible to create a copy of a
> component
Ok, but what was the bug/issue that was fixed by introducing
m_oldRootName? Before 2559 it was possible to create a copy of a
component by changing the value field and clicking save. Replacing a
component was done by creating a copy first and then deleting the old
one. After introducing m_oldRootNa
On 11/21/2010 4:49 PM, Marco Mattila wrote:
> This was changed in revision 2559. The reason was "Fix bug that
> prevented component from being replaced in library when the component
> root name was changed." I don't quite get the point, though. What
> exactly was the bug? Value != component name? I
On 22 November 2010 06:16, Karl Schmidt wrote:
> On 11/21/2010 06:03 PM, Brian Sidebotham wrote:
>>
>> I don't know what revision, but Jean-Pierre committed my patch for
>> fixing this on / around 22nd August. Email copies below:
>
> I'm talking about BZR 2615 which was new last week.
>
> Somethin
5 matches
Mail list logo
