ystrot / glance Goto Github PK

After an earlier search, I re-entered glance by my keyboard shortcut (cmd-f, I'm on a Mac).
My previously searched word is selected, except for the last character.

This is obviously a bug, the whole search string should be selected so I can directly type my next search.

My configuration:
OS 10.6 with Zend Studio 8.0

I have been using glance for a while. I love it! I recently upgrade to neon if I have glance open in a text editor and they try to use glance on the project explore or just select a file in the project explore eclipse hangs. I am using a Mac and I need to force quit eclipse. Attached is a complete eclipse log file

Glance Core 1.2.0.201609300916 com.xored.glance.feature.group xored software, Inc.

!SESSION 2017-01-22 10:35:23.453 -----------------------------------------------
eclipse.buildId=4.6.2.M20161124-1400
java.version=1.8.0_66
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -keyring /Users/ad/.eclipse_keyring
Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -keyring /Users/ad/.ecli
pse_keyring

This is a continuation of log file /Users/ad/workSpace/sc
eclipse_glance_crash_log.txt
/.metadata/.bak_0.log
Created Time: 2017-01-22 10:55:57.352

!ENTRY org.eclipse.ui 4 0 2017-01-22 10:55:57.352
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at com.xored.glance.ui.sources.ColorManager.getStore(ColorManager.java:50)
at com.xored.glance.ui.sources.ColorManager.(ColorManager.java:43)
at com.xored.glance.ui.sources.ColorManager.getInstance(ColorManager.java:55)
at com.xored.glance.ui.utils.TextUtils.applyStyles(TextUtils.java:53)
at com.xored.glance.ui.controls.text.styled.ListeningStyledTextSource.applyTextPresentation(ListeningStyledTextSource.java:92)
at com.xored.glance.ui.controls.text.styled.ListeningStyledTextSource.lineGetStyle(ListeningStyledTextSource.java:81)
at org.eclipse.swt.custom.StyledTextListener.handleEvent(StyledTextListener.java:49)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)

Hi,

please include a feature to allow the text field into which I enter the search string to get wider; either by making it expand automatically (as longer text is being entered) or horizontally expandable by mousedrag.
And/or just make it longer by default ;-)

Cheers,
Thomas

Looks like it doesn't work for Web Browser editor (i.e. when Javadoc is opened using "Open Attached JavaDoc in a Browser" feature). It would be particularly useful to have Glance working here, since standard Ctrl-F doesn't work here either.

This plug-in works great -- in its ease of use, it is a productivity booster. What I personally would find even more useful is to have quick text replace functionality. In terms of UI, I would imagine it to have just another textbox in the status bar. This would make the Glance plugin on par with Netbean's popular quick search functionality. Thanks.

I get a NullPointerException if glance search textbox is active/shown an then click on a tree node e.g. package/project explorer. Configuration dialog also seems to be broken.

Glance is really one of the most importent plugins to me!

Eclipse Java EE IDE for Web Developers.
Version: Neon Release Candidate 2 (4.6.0RC2)
Build id: 20160526-1324

!ENTRY org.eclipse.ui 4 0 2016-06-10 14:31:21.803 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at com.xored.glance.ui.sources.ColorManager.getStore(ColorManager.java:50) at com.xored.glance.ui.sources.ColorManager.<init>(ColorManager.java:43) at com.xored.glance.ui.sources.ColorManager.getInstance(ColorManager.java:55) at com.xored.glance.ui.controls.decor.StructDecorator.erase(StructDecorator.java:140) at com.xored.glance.ui.controls.decor.StructDecorator.handleEvent(StructDecorator.java:71) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4415) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088) at org.eclipse.swt.widgets.Tree.CDDS_ITEMPREPAINT(Tree.java:1058) at org.eclipse.swt.widgets.Tree.wmNotifyChild(Tree.java:7541) at org.eclipse.swt.widgets.Control.wmNotify(Control.java:5797) at org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:2033) at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:5351) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4827) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5120) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2446) at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1552) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4869) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:6074) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5107) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2446) at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1552) at org.eclipse.swt.widgets.Tree.WM_LBUTTONDOWN(Tree.java:6559) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4807) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:6074) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5107) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3819) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) at org.eclipse.equinox.launcher.Main.run(Main.java:1519)

are there any other ways to invoke glance in eclipse?
the full screen shortcut overrides the invoking.

When searching among projects in package explorer (may be, in other views, too), 'blue' color is used for selection. Looks like it's hard-coded. It should use the default system selection color.

Hi!

First of all thanks for all your efforts!

Feature Request:

1. Add button for "Clear search history".
2. Add additional setting for "Esc" to able/unable to "Close search box".

Eduard

Steps to reproduce:

1. open normal search
2. search for "hello"
3. open Glance search bar. Notice that there's not an "hello" string in search field
4. search for "there"
5. close Glance bar
6. open normal search

Current result:
normal search field contains "hello"

Expected result:
normal search field should contain "there". Furthermore at step 3 Glance field should contain "hello".

This is extremely useful if you want to search, type something and search again without getting focus to Glance bar again (I assigned ctrl+g and ctrl+shift+g as Find Next / Previous for both Glance and normal search).

If the Status Bar is not visible when a search has been carried out (ctrl + alt + f) the occurrences of the search are highlighted and gutter updated with matches however if you press enter to go to the next occurrence it will instead add a new line. There is no feedback that the status bar must be visible to use this feature.

To replicate ensure the Status Bar is not visible, this can be disabled by;

Window->Appearance->Hide Status Bar

Then select a search term and start glance (ctrl + alt + f) and then press enter.

Replicated using version 2018-09 (4.9.0).

I used to have glance installed in Eclipse and it was very useful. Now I'm using Aptana Studio but I can't get it installed. Is it Aptana-compatible?

I just write this into Aptana's own terminal: git clone git://github.com/ystrot/glance

And the installation seems to finish well but then I don't get anything from Ctrl+Shift+F

By the way it's Aptana Studio 3.4.0.2 running under Windows 8.

The update sit for glance is not working "www.exyte.com/glance/updates/". Is there any alternate upsate site available?

Some shortcuts can't be configured, for example ENTER or SHIFT+ENTER. Need to define them in Eclipse-way.

It would be cool to have this enhancement.

This way you could collapse all file, do a search with glance an show only the code of your interest.

The official Glance update site for Eclipse http://eclipse-glance.googlecode.com/svn/site/ is not available (down ?):

So currently you can't install Glance plugin (both thru Eclipse Marketplace and by dragging and dropping the "Install" button).

What steps will reproduce the problem?
Install Glance in eclipse

What is the expected output? What do you see instead?
Expected: Tree node highlight with blue background and white foreground (system default)
See: Tree node highlight with blue background and BLACK foreground

What version of the product are you using? On what operating system?
Glance version: 1.1.1
Eclipse version: 3.7.2
OS: Win7 pro x64

Additional info
After instaling and activating Glance in my eclipse, the highlighting of treeview nodes is somewhat broken. Usually the background is dark blue and the foreground (font color) is white. But after Glance the foreground color is black, which makes the highlighted text unreadable. If I switch off Glance, highlighting gets back to default (white font).

I wanted to attach a screenshot, but couldn't find a way how.

It seems that shortcut provided by Glance doesn't work well. This bug is pretty critical if for people who use keyboard shortcuts extensively.
It is expected that when You press "Glance Search" shortcut Glance will appear and text selected in editor will be typed into search box.

Steps to reproduce:

Tested on vanilla Eclipse 3.7.1 ("Eclipse IDE for Java Developers"(JDT), Version: Indigo Service Release 1, Build id: 20110916-0149) with Glance 0.7.6.200910031747

1. Create new untitled file for testing (File->New->Other->Untitled Text File)
2. Type in "qwe", new line(Enter), "asd" (2 lines total)
3. Select text "qwe" (double click in text in editor sould be ok)
   4 Press Ctrl+Alt+F - Glance will appear, and selected text is typed in search box (expected)
4. Select text "asd"
   6 Press Ctrl+Alt+F - Glance will appear, but selected text is not filled into search box (unexpected, "asd" should be in search box in this case)

At first I thought that the reason of such behavior is that "qwe" is already typed into search box before doing step 6, but it doesn't work even if search box is cleared.
Also, it seems that this bug is not 100% reproducible, on my STS it behaves slightly different (same with 0.7.6 and latest 0.9.1). Here is my observations:

1. Create new untitled file for testing
2. Type in "qwe", new line, "asd" (2 lines total)
3. Select text "qwe"
   4 Press Ctrl+Alt+F - Glance will appear, but selected text is not filled into search box (unexpected, "qwe" should be in search box in this case)
4. Select text "asd"
   6 Press Ctrl+Alt+F - Glance will appear, but selected text is not filled into search box (unexpected, "asd" should be in search box in this case)
5. Select text "qwe"
   8 Press Ctrl+Alt+F - Glance will appear, and selected text is typed in search box (expected, finally "qwe" is in search box)

Hi,
I am using oxygen on Mac.
After I perform a search and close the glance dialog, all editor/window where the search string was found is still highlighted or marked. Not with the same highlight color used by glance while glance is active, but still with a different background color and with all the occurrences showing up in the editor borders.

Hi there,
I found that I couldn't install glance from eclipse marketplace, and the url http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui seems not hold the latest 1.2.1 version.

Hi,

I have installed Glance in Eclipse 4.1 (Juno) at Linux (Debian v 6.0.6). I opened glance bar and a java file. I entered some word into Glance ant it's occurences were found.

But then I right-clicked on the tab related to opened java file and selected "Close". In error log I got "Unhandeled event loop exception" from org.eclipse.ui. NullPointer (stack trace below). From then on, many actions I did including usage of Error log view and opening the closed java file resulted with more Error log messages with NPE. Also, the Glance stopped finding the words it should have.

I have an RCP application that also uses glance, and it has similar problem on linux. However, on Windows 7 Proffesional, no such problem occurs.

Also, none of this happens if once closes an editor with the "x" sign, instead of right-click and Close. Only the Close (and Close All) causes this.

org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4361)
at org.eclipse.swt.SWT.error(SWT.java:4276)
at org.eclipse.swt.SWT.error(SWT.java:4247)
at org.eclipse.swt.widgets.Widget.error(Widget.java:480)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:417)
at org.eclipse.swt.widgets.Control.removeFocusListener(Control.java:1841)
at com.xored.glance.ui.controls.text.styled.TextSelector.dispose(TextSelector.java:39)
at com.xored.glance.internal.ui.viewers.SourceViewerControl.dispose(SourceViewerControl.java:65)
at com.xored.glance.ui.utils.UITextSource.dispose(UITextSource.java:63)
at com.xored.glance.internal.ui.search.SearchManager.setDescription(SearchManager.java:302)
at com.xored.glance.internal.ui.search.SearchManager.update(SearchManager.java:168)
at com.xored.glance.internal.ui.search.SearchManager.access$1(SearchManager.java:162)
at com.xored.glance.internal.ui.search.SearchManager$SourceListener.sourceChanged(SearchManager.java:406)
at com.xored.glance.internal.ui.sources.TextSourceListener.handleEvent(TextSourceListener.java:48)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1483)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1275)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1300)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1281)
at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:3619)
at org.eclipse.swt.widgets.Control.gtk_event_after(Control.java:2970)
at org.eclipse.swt.widgets.Tree.gtk_event_after(Tree.java:1906)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1753)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5116)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3459)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4369)
at org.eclipse.swt.internal.gtk.OS._gtk_widget_grab_focus(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_widget_grab_focus(OS.java:13088)
at org.eclipse.swt.widgets.Tree.gtk_button_press_event(Tree.java:1869)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1746)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5116)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3459)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4369)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8307)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1192)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2332)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3177)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

1. Move old issues to github.
2. Mark project on google code as deprecated.

Hello,

Would it be possible to have an option that goes backward on the search when deleting some characters of the search string ?

Maybe an example will be more explicit :
you're at line 150, looking incrementally for the string "buffer" : you start typing b, then u, then f (twice), and find what you were looking for at line 300. Now, you would like to go back to where you started your search, and you start deleting the string you wrote, but you stay at line 300, while I would find it useful to have the possibility to go back (incrementally, of course :) )

This incremental behaviour is the one in vim (and emacs I think) if you would like to try (open a file in vim and type :set incsearch).

And by the way, thanks for glance, it's really a great plugin

Currently I can do following:

• open glance panel
• move back to control
• select something
• move back to glance panel

Selection is still here, but it should disappear like on startup.

The glance panel should be shown on the bottom of the current view (eg. the package explorer).
But instead it is shown in the status bar:

I have macOS 10.12.6 (16G29)
Eclipse 4.7

searching inside git log history shows text duplicated with a little offset, something like double vision or blurred text.

Closing glance search clean the view, and solves the problem

The problem is when you already has and open glance search in text editor and open a history view, this problem arises by itself, It took me a while to notice the blur comes from glance search

Was originally requested here: http://code.google.com/p/eclipse-glance/issues/detail?id=23

The history view is stripped from many graphical information, making the view useless.

Looks like Git History View needs special support from the Glance side.

Hope to finish media part soon :-)

according to instructions, the shortcut to open the Glance window is command-control-F. But, that shortcut, on a macbook pro means 'maximize current window'. Can this shortcut be re-assigned to some other key sequence?

Thanks, Edwin

Any way to install glance as repository, but calling from github instead http://eclipse-glance.googlecode.com/svn/site/ ?

Eclipse 4.9 (but this problem has been here for as long as I can remember)
Linux 64 bits

In Glance Preferences, change the highlight color, Apply and Close. Works fine.
Restart Eclipse: colors are back to default settings.

As far as I can tell, the other settings are remembered properly.

After I install Glance, ctrl+alt+f (on Linux) opens Glance find box. However, the normal Eclipse Find/Replace dialog can no longer be opened using ctrl+f. The key still seems to be registered (Window menu, Preferences menu item, General category, Keys category, 'Find and Replace' command). Opening it via the Edit menu and then the 'Find/Replace...' menu item still works. It there also still shows the ctrl+f shortcut key next to the menu item... Since Glance doesn't support replace, it would be nice if the original dialog could still be accessed using ctrl+f.

As it can be seen in the image the bottom border is cut of in the search text box.

ystrot,

First off this plugin is great -- I've been using it daily and telling other developers about it who have also begun using it.

Would it be possible to add expanded support for table views like you see in the Package Explorer and debug variable windows? Currently, you can search the package explorer and matches will only be returned for previously expanded folders. It would be helpful if the plugin could crawl the graph structure in this circumstance and expand all the nodes that match your search criteria.

Thanks again for the great work!

Not finding any matches in .h or other non-C) files (C-only project).
Edited the "in:" window contents to ".c,.h,*.py", etc. It only ever matches items in .c files.
Running in Eclipse 2021-09 (4.21.0), Build id: 2021-910-1417.
OS: per uname -1: Linux 4.9.0-16-amd64 #1 SMP Debian 4.9.272-1 (2021-06-21) x86_64 GNU/Linux

Moved from http://code.google.com/p/eclipse-glance/issues/detail?id=15

I see this feature in the plugin "highlight" to jedit.
I am looking for a plugin that does this for some time.

Hey,
i'm getting the following error when running Glance (1.1.1)

I'm running on CentOS 6 and the problem seems to happen with PyDev (2.7.1.2012100913) installed (not sure if thats the problem) The outline window seems to mess up (All text goes white) and when i mouse over t the error log keeps posting
Unhandoled event loop exceptions.

I installed glance and pydev directly from the marketplace.

My system session data is :
eclipse.buildId=M20120914-1800
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product

The Exception Stack Trace is :

java.lang.NullPointerException
at com.xored.glance.ui.controls.decor.StructSource.getCell(StructSource.java:53)
at com.xored.glance.ui.controls.decor.StructDecorator.paint(StructDecorator.java:83)
at com.xored.glance.ui.controls.decor.StructDecorator.handleEvent(StructDecorator.java:68)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1300)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1285)
at org.eclipse.swt.widgets.Tree.rendererRenderProc(Tree.java:2702)
at org.eclipse.swt.widgets.Display.rendererRenderProc(Display.java:1316)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8307)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1192)
at org.eclipse.swt.internal.gtk.OS._gdk_window_process_all_updates(Native Method)
at org.eclipse.swt.internal.gtk.OS.gdk_window_process_all_updates(OS.java:5561)
at org.eclipse.swt.widgets.Display.update(Display.java:4322)
at org.eclipse.swt.widgets.Display.runDeferredLayouts(Display.java:3580)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3166)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

Not able to install it on my eclipse , it is saying that location not avaliable

Hi, glance is really cool, exactly what I was looking for. However whenever I use it after a while (say an hour or so) I end up with the exception attached at the end of this bug.. I have to restart eclipse in order for everything to work properly again.

I'm using glance 1.0.0 as downloaded from the marketplace, and eclipse 3.7.2 under arch linux with openjdk 7.b147_2.1-3

!ENTRY org.eclipse.ui 4 0 2012-05-18 20:04:38.019 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at com.xored.glance.ui.controls.text.styled.TextSelector.dispose(TextSelector.java:39) at com.xored.glance.internal.ui.viewers.SourceViewerControl.dispose(SourceViewerControl.java:65) at com.xored.glance.ui.utils.UITextSource.dispose(UITextSource.java:63) at com.xored.glance.internal.ui.search.SearchManager.setDescription(SearchManager.java:288) at com.xored.glance.internal.ui.search.SearchManager.update(SearchManager.java:157) at com.xored.glance.internal.ui.search.SearchManager.access$1(SearchManager.java:152) at com.xored.glance.internal.ui.search.SearchManager$SourceListener.sourceChanged(SearchManager.java:389) at com.xored.glance.internal.ui.sources.TextSourceListener.handleEvent(TextSourceListener.java:48) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1531) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1257) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263) at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:3575) at org.eclipse.swt.widgets.Control.gtk_event_after(Control.java:2938) at org.eclipse.swt.widgets.Tree.gtk_event_after(Tree.java:1956) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1738) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5016) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3530) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4408) at org.eclipse.swt.internal.gtk.OS._gtk_widget_grab_focus(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_widget_grab_focus(OS.java:12956) at org.eclipse.swt.widgets.Tree.gtk_button_press_event(Tree.java:1919) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1731) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5016) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3530) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4408) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1245) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386)

When a part of source code in a text editor is collapsed (folded), and a search result is 'displayed' for a part of that text, the text is not expanded (unfolded), making the highlighted text invisible. In then seems like Glance is not highlighting anything, causing confusion. Normal Eclipse find feature expands text that contains the find result, to make sure it is visible. It would be nice if Glance could do this as well.

It would be helpful to be able to sort the search results by any column. Alternatively (or as well), to be able to Select All and Copy search results for sorting elsewhere.

For Path, multiple sort options are possible: by filename, extension, file path, ...

Moved from http://code.google.com/p/eclipse-glance/issues/detail?id=20

It is handy to use glance to highlight text occurences within editor to analyse sourse code. However, if user type some text within search edit box cusror position gets instantly moved to matched occurence(incremental search) which may be very confusing.
Let me explain. Lets assume You are reading source code with 1000 lines and currently viewing some method implementation on line 500. You want to check is there any useage of variable "qwe", so you type "qwe" in glance search edit box to highlight all occurences of "qwe". If the next occurence is visible to You without having to scroll editor - there is no problem - the occurence highlighted and You can continue Your analysis. If the next ocurence located, say on line 900 or 150 - cursor position chenged, editor scrolled and You loose Your focus on what You have been doing before(now You have to realize where You are now and where were You before to come back and continue Your analysis). Moreover, if there is no occurence at all - You will be moved to some random part of the sorce code(You have to type keyword letter by letter, and glance will move you first to occurence of "q", then "qw" and only then to "qwe").
I have a suggestion how to fix this usability issue. To aid this issue it would be great to have an option to disable "incremental searching", but still highlight occurences.
Here is the use case for such behaviour. You type "qwe" into glance search edit box. All occurences of "qwe" in current editor got highlighted, no moving cursor to the next occurence. To move cursor to the next occurence You press enter in search edit box(just like with standard search).
This should allow user both possibility to highlicht occurences without confusing him by jumping through source code and be able to use glance to search text occurences.

Hi,

I installed Glance (1.2.1.201702271753 com.xored.glance.feature.group, xored software, Inc.) from the Eclipse Marketplace (https://marketplace.eclipse.org/content/glance).

I'm experiencing Bug 520413 / Bug 520450, which seems to have been fixed with this Gerrit change: https://git.eclipse.org/r/#/c/102880/

But the change doesn't seem to be merged into the Plugin on the marketplace or the code in this Github repo. Is there a Glance version/build with all the latest fixes?

The version available from e4 is "Eclipse Glance - Incremental text search 0.0.1.v20171117-1039", which looks older from the version number.

Moved from http://code.google.com/p/eclipse-glance/issues/detail?id=11

The standard Ctrl-F search is a non-modal window, so you can still search,
type and scroll trough the window while having a search window on top. It
would be great if glance search popup worked similarly. That would help
with navigating to highlighted text appearances using markers on right
Editor navigation bar.

I see very strange behavior in the project explorer window when installed on a 64 bit version of eclipse. I'm currently running the version below but have seen this on previous Mars and Neon releases. It would be great to get his fixed as It's one of my favorite additions to eclipse.

Eclipse for Parallel Application Developers
Version: Neon Milestone 7 (4.6.0M7)
Build id: 20160505-1310