Agreed.
Another equivalent common term in the industry is WAI or "works as
intended".
Andrew
On Sat, Oct 12, 2019 at 6:10 PM Strontium wrote:
> My 2c
>
> "As Designed" should be the only answer. Bug is subjective. If the
> user thinks the designed behaviour is
> broken then they will always t
My 2c
"As Designed" should be the only answer. Bug is subjective. If the
user thinks the designed behaviour is
broken then they will always think of it as a bug. Invalid is worse,
because yes it tells the user they are an idiot.
Even if the program is working "As Designed" it does not mean
Hi Sylwester,
Please keep in mind that wxUpdateUIEvents are generated in response to
wxCommandEvents which are typically generated by menu, toolbars, and
buttons. Other control events will not fire a wxUpdateUIEvent so using
them will have no affect for things like checking a wxCheckBox control
o
The main thing I didn’t like in the Launchpad workflow was the “Invalid” tag.
After one of our users spends a lot of time (or even a little) logging a bug,
it often gets their back up if you mark it “invalid”.
(In the past I’ve used systems that labelled this either “Not a Bug” or “As
Designed
The document is still open for comments on
https://docs.google.com/document/d/1pRcqXIXSn1_Ep2mYtSnoJWFahi9fMx4UJ8UEwFFwLkQ/edit?usp=sharing
On Thu, 10 Oct 2019 at 11:30, Ian McInerney wrote:
>
> On a similar note, the issue workflow will need to be modified if the GitLab
> tracker is used. Unfor
Hi Wayne,
In the light of below finding, is this review comment still valid?
It belonged to my changes for initial conditions[1].
Dnia 27 czerwca 2019 21:04 Wayne Stambaugh
napisał(a):
> Get rid of DIALOG_SIM_SETTINGS::disableCtrlOnCheckboxEvent() and use the
> appropriate wxUpdateUIEvent[1]
6 matches
Mail list logo
