Bug 11925 - Size of component popup window incorrect (doesn't fit), when i click on function names or typenames on top of document.
Summary: Size of component popup window incorrect (doesn't fit), when i click on funct...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.0.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: David Siegel
Depends on:
Reported: 2013-04-23 21:00 UTC by newbprofi
Modified: 2013-05-13 11:27 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description newbprofi 2013-04-23 21:00:54 UTC
On top of every text document there is shortcuts of current editing type and function.
So when i click on it, i see popup window that fits only current (clicked) name, but doesn't fit (by width) all names in window. So i don't see full names in that window.
Comment 1 Mike Krüger 2013-05-03 09:25:57 UTC
We've limited the size of that window - it was a design decision. Otherwise the window could grow very large - therefore we ellipsise the window at a certain width.
Comment 2 Mike Krüger 2013-05-03 09:26:32 UTC
@newbprofi: can you make a screenshot ? Maybe we were a bit too restrictive about the window size.
Comment 3 newbprofi 2013-05-10 16:20:27 UTC
You solving bugs by deleting them? gj kiddo.
Comment 4 newbprofi 2013-05-10 16:20:50 UTC
Go f4ck yourself.
Comment 5 newbprofi 2013-05-10 16:33:05 UTC
Oh and btw, try to test your bugsh1t Editor, before release. Visual Studio was never needed a singe bug report, especially for TextEditor. I found >10 most obvious and most used bugs in your trash for 30 mins of using. Try harder clouns. AFAIK.
Comment 6 newbprofi 2013-05-10 16:43:56 UTC
I just discovered that my bug reports was only disappeared in my list, but not deleted.

But anyway, you was needed hard critique for better work. May be someday you will learn to test your products.
Comment 7 newbprofi 2013-05-10 18:22:39 UTC
Clowns. You can't even make and test properly simple TEXT EDITOR. lol. I am afraid even imagine how much bugs still inside of your MONO implementation of .NET. 

Especially when i've seen how you solve bug reports, by just closing them or setting it FIXED, when it's not FIXED. Lol really clowns.
Why you need "bug reports" if you do so?

As i said, just hire good testers and good code quality/bugs viewers (30+ age, 10+ programming experience). And try to make products without bugs. Like developers of Visual Studio do. Then you will not need bug reports, anyway you are useless with it.
Comment 8 newbprofi 2013-05-10 18:28:29 UTC
No more bug reports from me. You must do usable product, yourself. 

I must be able to use your product at least 30 minutes without bugs, i dont even ask 1 day - you are not ready for this. Until that, your bugged sh1t is totally useless for me. Next time i will try your sh1t only at version 5.0+. You have some time to learn lessons.
Comment 9 PJ 2013-05-13 11:27:07 UTC
Unfortunately, we can only take useful bug reports. RESOLVing as INVALID. If you have a few minutes to compose a real bug report, please re-post. 

Thank you for your time, and for trying Xamarin.