I guess we are talking about m_ProjectProperties.FindBugID.
But it is already called when there is a BugTraqProvider (at the end of
OnBnClickedBugtraqbutton).
So the project properties are already there, is there any reason we can't
use them in CCopyDlg::OnBnClickedHistory ?
On Tuesday, Februar
On Monday, February 26, 2018 at 9:38:05 AM UTC+1, Balázs wrote:
>
> Thank you for the reply.
> Could you please explain what do you mean under "reading properties"?
> All I see is the list of recent messages contains the same lines as in the
> ordinary commit dialog.
> The only difference to the
Thank you for the reply.
Could you please explain what do you mean under "reading properties"?
All I see is the list of recent messages contains the same lines as in the
ordinary commit dialog.
The only difference to the user is that the Bug-ID editbox is not updated
on selecting a message from t
That's actually expected: reading properties remotely is very slow, so in
the repo browser the properties are not read and therefore not used.
--
You received this message because you are subscribed to the Google Groups
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emai
It is a minor issue but causes some inconsistent user experience.
bugtraq:message is set to "ID=%BUGID%" in the whole repository so the
"Bug-ID / Issue-Nr:" editbox appears on the Commit Dialog.
When I select a recent message where the ID is set, this number is
automatically extracted from the m
