Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » FastPartitioner's documentChanged2()/documentToBeChanged() are called via the Reconciler's thread?
FastPartitioner's documentChanged2()/documentToBeChanged() are called via the Reconciler's thread? [message #323155] Wed, 12 December 2007 05:16 Go to next message
Alex Le is currently offline Alex LeFriend
Messages: 649
Registered: July 2009
Senior Member
Thanks.
Re: FastPartitioner's documentChanged2()/documentToBeChanged() are called via the Reconciler's threa [message #323156 is a reply to message #323155] Wed, 12 December 2007 05:19 Go to previous message
Alex Le is currently offline Alex LeFriend
Messages: 649
Registered: July 2009
Senior Member
AL wrote:
> Thanks.

Looks like it does *not*...

Document(AbstractDocument).updateDocumentStructures(Document Event)
line: 633
Document(AbstractDocument).fireDocumentChanged(DocumentEvent ) line: 720
Document(AbstractDocument).replace(int, int, String, long) line: 1081
Document(AbstractDocument).replace(int, int, String) line: 1091
DefaultDocumentAdapter.replaceTextRange(int, int, String) line: 248
StyledText.modifyContent(Event, boolean) line: 5757
StyledText.sendKeyEvent(Event) line: 6500
StyledText.doBackspace() line: 2111
StyledText.invokeAction(int) line: 5645
StyledText.handleKey(Event) line: 5033
StyledText.handleKeyDown(Event) line: 5054
StyledText$7.handleEvent(Event) line: 4800
EventTable.sendEvent(Event) line: 66
StyledText(Widget).sendEvent(Event) line: 938
StyledText(Widget).sendEvent(int, Event, boolean) line: 962
StyledText(Widget).sendEvent(int, Event) line: 947
StyledText(Widget).sendKeyEvent(int, int, int, int, Event) line: 975
StyledText(Widget).sendKeyEvent(int, int, int, int) line: 971
StyledText(Widget).wmChar(int, int, int) line: 1285
StyledText(Control).WM_CHAR(int, int) line: 3772
StyledText(Control).windowProc(int, int, int, int) line: 3672
StyledText(Canvas).windowProc(int, int, int, int) line: 291
Display.windowProc(int, int, int, int) line: 4351
OS.DispatchMessageW(MSG) line: not available [native method]
OS.DispatchMessage(MSG) line: 2264
Display.readAndDispatch() line: 3291
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2389
Workbench.runUI() line: 2353
Workbench.access$4(Workbench) line: 2219
Workbench$4.run() line: 466
Realm.runWithDefault(Realm, Runnable) line: 289
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 461
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
IDEApplication.start(IApplicationContext) line: 106
EclipseAppHandle.run(Object) line: 153
EclipseAppLauncher.runApplication(Object) line: 106
EclipseAppLauncher.start(Object) line: 76
EclipseStarter.run(Object) line: 363
EclipseStarter.run(String[], Runnable) line: 176
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not
available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: not available
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: not available
Method.invoke(Object, Object...) line: not available
Main.invokeFramework(String[], URL[]) line: 504
Main.basicRun(String[]) line: 443
Main.run(String[]) line: 1169
Main.main(String[]) line: 1144
Previous Topic:Possible bug in FastPartitioner
Next Topic:Programatically updating the javadoc and declaration view
Goto Forum:
  


Current Time: Sat Aug 17 09:17:00 GMT 2024

Powered by FUDForum. Page generated in 0.03915 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top