|
Bugzilla – Full Text Bug Listing |
| Summary: | ncurses - False positive error: YWidget.cc(setKeyboardFocus):359 Widget `next cannot accept the keyboard focus. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Lukas Ocilka <locilka> |
| Component: | YaST2 | Assignee: | Katarina Machalkova <kmachalkova> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Alpha 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Well, and why exactly is this a problem? Because it fills up y2log with <3> errors. But these errors are maximally <2> warnings. - - - <2> Widget `next cannot accept the keyboard focus, button disabled. - - - So: 'minor' or 'enhancement' ;)? The msg actually comes from y2-core (libyui) and appears only in curses, because y2-qt child class (unlike curses) has its own definition of setKeyboardFocus method and thus overrides the virtual one from the parent Anyway, fixed in svn |
It seems that ncurses library badly identifies an exception. YWidget.cc(setKeyboardFocus):359 Widget `next cannot accept the keyboard focus. Is returned even if the `next button exists -- but it's disabled. Qt don't report it as an error... --- testcase --- { import "Wizard"; Wizard::CreateDialog(); Wizard::SetContents ( "", `Empty(), "", false, false ); // Wizard::DisableAbortButton(); //used in installation UI::UserInput(); Wizard::CloseDialog(); } --- testcase --- Well, this actually needn't be false-positive error, but I'd expect a warning level at maximum.