Bug 326683 - Compare blocks UI even if chosen to run in background
Summary: Compare blocks UI even if chosen to run in background
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on: 324993
Blocks:
  Show dependency tree
 
Reported: 2010-09-30 11:06 EDT by Dani Megert CLA
Modified: 2019-11-14 03:40 EST (History)
4 users (show)

See Also:

Attachments
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 Dani Megert CLA 2010-09-30 11:06:02 EDT 
I20100928-1200.

1. disable to use the capping algo
2. set preference to always run in background
3. compare two very large files with each other (e.g.:
   /org.eclipse.jdt.ui/dictionaries/en_GB.dictionary
  /org.eclipse.jdt.ui/dictionaries/en_US.dictionary
==> dialog pops-up blocking further work
Comment 1 Tomasz Zarna CLA 2010-09-30 12:00:52 EDT 
I think the only way to address this is to fix bug 324993.
Comment 2 Dani Megert CLA 2010-10-01 02:00:19 EDT 
(In reply to comment #1)
> I think the only way to address this is to fix bug 324993.
I agree that using jobs would be better.
Comment 3 Dani Megert CLA 2011-03-22 09:19:37 EDT 
Switching to jobs so late in the 3.7 cycle seems unreasonable. Suggest to fix for 3.8.
Comment 4 Szymon Brandys CLA 2012-05-02 10:08:48 EDT 
Would be nice to have it fixed, but no-one from Platform Workspace team is looking at it and most likely no-one will be looking at it during 4.3. Any help is welcome.
Comment 5 Lars Vogel CLA 2019-11-14 03:40:50 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.