Bug 312939 - [Progress] "name" parameter in ProgressManager(org.eclipse.ui.internal) beginTask is too restrictive
Summary: [Progress] "name" parameter in ProgressManager(org.eclipse.ui.internal) begin...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-14 12:33 EDT by Miwako Tokugawa CLA
Modified: 2019-09-06 15:31 EDT (History)
2 users (show)

See Also:

Attachments
screenshot (22.12 KB, image/pjpeg)
2010-05-14 13:04 EDT, Miwako Tokugawa CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Miwako Tokugawa CLA 2010-05-14 12:33:30 EDT 
Build Identifier: Any

It seems that I can only use a single-line string in the "name" parameter (If I specify, say, "line1\nline2". Also a longer single-line string is truncated. Could you support longer/multi-line strings?

Reproducible: Always
Comment 1 Remy Suen CLA 2010-05-14 12:42:02 EDT 
(In reply to comment #0)
> It seems that I can only use a single-line string in the "name" parameter (If I
> specify, say, "line1\nline2". Also a longer single-line string is truncated.

I presume you're talking about the 'Progress' view, yes?
Comment 2 Miwako Tokugawa CLA 2010-05-14 13:04:54 EDT 
Created attachment 168566 [details]
screenshot

>I presume you're talking about the 'Progress' view, yes?
Yes, I think so. I attached the screenshot.
Comment 3 Remy Suen CLA 2010-05-14 13:06:22 EDT 
Thank you for your screenshot, Miwako.
Comment 4 Prakash Rangaraj CLA 2010-05-17 00:24:52 EDT 
Looking at it
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:31:15 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.