Re: [Subclipse-users] History Window Icons getting displayed in my editor

On Fri, Feb 15, 2008 at 7:19 AM, Puneet Lakhina
<puneet.lakhina_at_gmail.com> wrote:
> I dont know too much about eclipse plugin development, so some of the
> terminologies I use here might be incorrect.
> I have a rather strange problem. I am using eclipse 3.2 with Subclipse
> 1.2.4. While working in the java perspective, I opened the history
> window for a file through Team->Show history.This opened in the
> section of tabs at the bottom right hand corner of my window (This
> section has other tabs like problems,console etc). Now I went back to
> my Java editor window in full screen mode. Now I saved my file (Ctr+s
> or ctr+shift+s). What this results in is the row of action icons from
> the history window (The referesh,link editor with selection, print,
> search history, clear history, show comments, show affected paths,
> next 20 and get all) get displayed over the top of my editor. "Over
> the top" here signifies as having a greater z-index. Their location is
> approximately where they will be if i exited the full screen view of
> my editor. Everytime I do a save, they like hop to the left a bit and
> return to the same location.
>
> Also, once I exit my full screen view, and then do a full screen again
> (Ctr+M) these icons disappear only to appear again on the next save.
> If i move the history window to a different section, everything stays
> normal.I have even tried exchanging the position of say the console
> window in the same section with the history window, and that doesnt
> result in any problem. Its only with the history window when its at
> the last position in this section.
>
> I dont know if its an eclipse issue or a subclipse issue, but since it
> was happening with the history window, I am posting this here. I would
> be more than happy to provide any details, screenshots if that helps.
> I havent tried restarting eclipse as I am not too much a fan of the
> "restart and see" solution :-).

I have never seen this myself. I tend to think it has to be an
Eclipse issue. When weird things like this happen, I usually ask
myself a question like "If I wanted to write code to make this problem
happen intentionally could I?" I think the answer here is No.
Therefore, it would seemingly be an Eclipse bug.

I am certainly open to suggestions to fix if others see it.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org