|
Bugzilla – Full Text Bug Listing |
| Summary: | Report.ycp should support long messages | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jiri Srain <jsrain> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
After 10.0 |
From yast2-hacker mailing list (probably for after 10.0): Dne čtvrtek 18 srpen 2005 23:21 Reed Haslam napsal(a): > Are there YaST2 guidelines for handling LONG error messages. > > We have a few that we know run off the screen in text mode installs. > > Would it not be possible for the low level Report::Error() and similar > routines to handle text wrapping and thus allow the caller to simply > pass one long string without any "\n"? > > If that is not going to be done, what are the guidelines for handling > long error messages in YaST2? What is possible is to use a popup including RichText widget, which does line breaks automatically. It shouldn't be problem to implement something like Report::LongError () and similar which would use RichText instead of labels. It also gives scrolling for extra long error messages.