Bug 106076 - Report.ycp should support long messages
Summary: Report.ycp should support long messages
Status: RESOLVED DUPLICATE of bug 79161
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 2
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Ladislav Slezák
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-22 07:07 UTC by Jiri Srain
Modified: 2005-09-14 06:54 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Srain 2005-08-22 07:07:30 UTC
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.
Comment 1 Ladislav Slezák 2005-08-22 14:15:27 UTC
After 10.0
Comment 2 Ladislav Slezák 2005-09-14 06:54:47 UTC

*** This bug has been marked as a duplicate of 79161 ***