Reshaper 2.0 oddness, notes, and questions

I'm using Resharper 2.0 on VS.Net 2003, using exclusively C# projects and
solutions.

First thing I noticed was that the red/yellow/green colors for the little
box have change shades. Just saying I think I prefer the original shades
significantly to these more 'bright' versions.

Second thing I noticed was that the lightbulb pop-up is bright magenta. I
hope that's not on purpose, and that it's SUPPOSED to be transparent.

And to make a liar out of myself, the REAL first thing I noticed was
performance. I expect there's debug and unoptimized code in there, but just
starting up VS.Net 2003 for the first time took MINUTES and MINUTES, with
msdev.exe chewing up the CPU. When it FINALLY loaded up, it took even
longer to load up my relatively modest solution (only three projects, but a
hundred or so files). MUCH longer than before (several times as long).

The 'outline brackets' feature was unexpected. I'm going to try it for a
while to see if I prefer it, or just the coloring of the brackets, but it
caught me off guard at first.

I also noticed the solution opened with the "file structure window" and
"test runner window" as these small floating windows, already open. Was
that intentional? I really don't think those should default to being
displayed like that.

And what's "EnableDaemon" (resharper key Ctrl+8)? And maybe it could have a
more descriptive name?

There's also lots of "TOOLzzzXXXzzz" entries in the Resharper key maps,
where "XXX" is some legitimate command name.

Also, no sign of "Complete Statement"... any idea when that'll be coming?


20 comments
Comment actions Permalink

First thing I noticed was that the red/yellow/green colors for the little
box have change shades. Just saying I think I prefer the original shades
significantly to these more 'bright' versions.


Small issue, but I agree with you.

>

Second thing I noticed was that the lightbulb pop-up is bright magenta. I
hope that's not on purpose, and that it's SUPPOSED to be transparent.


This has to be someone forgetting to set the transparency color. I hope

>

And to make a liar out of myself, the REAL first thing I noticed was
performance. I expect there's debug and unoptimized code in there, but
just starting up VS.Net 2003 for the first time took MINUTES and MINUTES,
with msdev.exe chewing up the CPU. When it FINALLY loaded up, it took
even longer to load up my relatively modest solution (only three projects,
but a hundred or so files). MUCH longer than before (several times as
long).

>

I did not have the same experience, in fact I find it to be faster that 1.5.
On a solution with 11 projects.

The 'outline brackets' feature was unexpected. I'm going to try it for a
while to see if I prefer it, or just the coloring of the brackets, but it
caught me off guard at first.

>

The outline is ugly, I prefer the coloring.

I have an issue with Reformat Code, on my base classes it works fine, but on
my child classes I cannot use it, it is grayed out.


0
Comment actions Permalink

re: the magenta background to the lightbulb... after restarting, it went
away, and looks acceptable. However, the behavior is slightly weird. The
surrounding box and down-arrow only appears when the arrow is exactly over
the image of the bulb. Move the cursor off the bulb, and the box and the
down-arrow disappear... now, given that the down-arrow looks like something
you could or should click on to see the options, this is bad. In fact,
since clicking on the bulb does exactly what you think it should, I wonder
why the box/down-arrow thing is there at all?

For the record, even on subsequent restarts, the start-up time of VS.Net
2003 is really, really, really slow.

"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dbk0ur$c54$1@is.intellij.net...

I'm using Resharper 2.0 on VS.Net 2003, using exclusively C# projects and
solutions.

>

First thing I noticed was that the red/yellow/green colors for the little
box have change shades. Just saying I think I prefer the original shades
significantly to these more 'bright' versions.

>

Second thing I noticed was that the lightbulb pop-up is bright magenta. I
hope that's not on purpose, and that it's SUPPOSED to be transparent.

>

And to make a liar out of myself, the REAL first thing I noticed was
performance. I expect there's debug and unoptimized code in there, but
just starting up VS.Net 2003 for the first time took MINUTES and MINUTES,
with msdev.exe chewing up the CPU. When it FINALLY loaded up, it took
even longer to load up my relatively modest solution (only three projects,
but a hundred or so files). MUCH longer than before (several times as
long).

>

The 'outline brackets' feature was unexpected. I'm going to try it for a
while to see if I prefer it, or just the coloring of the brackets, but it
caught me off guard at first.

>

I also noticed the solution opened with the "file structure window" and
"test runner window" as these small floating windows, already open. Was
that intentional? I really don't think those should default to being
displayed like that.

>

And what's "EnableDaemon" (resharper key Ctrl+8)? And maybe it could have
a more descriptive name?

>

There's also lots of "TOOLzzzXXXzzz" entries in the Resharper key maps,
where "XXX" is some legitimate command name.

>

Also, no sign of "Complete Statement"... any idea when that'll be coming?



0
Comment actions Permalink

>> And to make a liar out of myself, the REAL first thing I noticed was
>> performance. I expect there's debug and unoptimized code in there, but
>> just starting up VS.Net 2003 for the first time took MINUTES and MINUTES,
>> with msdev.exe chewing up the CPU. When it FINALLY loaded up, it took
>> even longer to load up my relatively modest solution (only three
>> projects, but a hundred or so files). MUCH longer than before (several
>> times as long).
>>
>

I did not have the same experience, in fact I find it to be faster that
1.5. On a solution with 11 projects.


Strange. My problem persists. Loading up an empty Visual Studio.Net 2003
takes several times as long as before. Ditto loading up a simple C#
solution with three projects and a hundred or so files (only a few of the
files are of significant length). It's not just 'noticably' slower. It's
many times slower. Still.


>> The 'outline brackets' feature was unexpected. I'm going to try it for a
>> while to see if I prefer it, or just the coloring of the brackets, but it
>> caught me off guard at first.
>>
>

The outline is ugly, I prefer the coloring.


I changed the color of the outline to light-gray from dark-gray, and it's
much less offensive. I think I can get used to it and even like it. You
might want to give that a try.

I have an issue with Reformat Code, on my base classes it works fine, but
on my child classes I cannot use it, it is grayed out.


I haven't noticed this yet, but I'll keep an eye out for it.


0
Comment actions Permalink

Just to quantify the numbers... with Resharper 1.5, loading an empty Visual
Studio.Net (just a start page, no solution) takes well under 5 seconds from
cliking on the launch icon to being ready to work.

With Resharper 2.0, it takes a full 60 seconds to get to that point, most of
it just staring at the splash screen.


"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dbkkvl$dkv$1@is.intellij.net...
>>> And to make a liar out of myself, the REAL first thing I noticed was
>>> performance. I expect there's debug and unoptimized code in there, but
>>> just starting up VS.Net 2003 for the first time took MINUTES and
>>> MINUTES, with msdev.exe chewing up the CPU. When it FINALLY loaded up,
>>> it took even longer to load up my relatively modest solution (only three
>>> projects, but a hundred or so files). MUCH longer than before (several
>>> times as long).
>>>
>>
>> I did not have the same experience, in fact I find it to be faster that
>> 1.5. On a solution with 11 projects.
>

Strange. My problem persists. Loading up an empty Visual Studio.Net 2003
takes several times as long as before. Ditto loading up a simple C#
solution with three projects and a hundred or so files (only a few of the
files are of significant length). It's not just 'noticably' slower. It's
many times slower. Still.

>
>
>>> The 'outline brackets' feature was unexpected. I'm going to try it for
>>> a while to see if I prefer it, or just the coloring of the brackets, but
>>> it caught me off guard at first.
>>>
>>
>> The outline is ugly, I prefer the coloring.
>

I changed the color of the outline to light-gray from dark-gray, and it's
much less offensive. I think I can get used to it and even like it. You
might want to give that a try.

>
>> I have an issue with Reformat Code, on my base classes it works fine, but
>> on my child classes I cannot use it, it is grayed out.
>

I haven't noticed this yet, but I'll keep an eye out for it.

>



0
Comment actions Permalink

Paul,

Thank You for the feedback. I'll comment some of the point You've.
mentioned.

Second thing I noticed was that the lightbulb pop-up is bright magenta. I
hope that's not on purpose, and that it's SUPPOSED to be transparent.

Unfortunately, it happens from time to time, but I cannot definitely
reproduce such behavior. In most cases switching to another application and
getting back solves the problem. If You have an idea, how to get this
magenta effect on demand, it will help a lot.

And to make a liar out of myself, the REAL first thing I noticed was
performance. I expect there's debug and unoptimized code in there, but
just starting up VS.Net 2003 for the first time took MINUTES and MINUTES,
with msdev.exe chewing up the CPU. When it FINALLY loaded up, it took
even longer to load up my relatively modest solution (only three projects,
but a hundred or so files). MUCH longer than before (several times as
long).

Performance is our main concern. We are working on it.

I also noticed the solution opened with the "file structure window" and
"test runner window" as these small floating windows, already open. Was
that intentional? I really don't think those should default to being
displayed like that.

VS tracks the tool windows appearence according to her own strategy, and the
only possible things we are able to do is not to show the windows at the
first start until they are requested to show.

And what's "EnableDaemon" (resharper key Ctrl+8)? And maybe it could have
a more descriptive name?

This feature toggles file highlighting on/off. Maybe the name is not so good
:)

There's also lots of "TOOLzzzXXXzzz" entries in the Resharper key maps,
where "XXX" is some legitimate command name.

These are the commands to activate our tool windows. We'll change the
command names.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Thank you for the feedback.

The GREAT start-up slowdown is the known issue is the major one.
We we deal with it urgently.

Did you see any noticable slow-down AFTER the solution is opened? I.e. in
regular work?

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dbkquo$b9$1@is.intellij.net...

Just to quantify the numbers... with Resharper 1.5, loading an empty
Visual Studio.Net (just a start page, no solution) takes well under 5
seconds from cliking on the launch icon to being ready to work.

>

With Resharper 2.0, it takes a full 60 seconds to get to that point, most
of it just staring at the splash screen.

>
>

"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dbkkvl$dkv$1@is.intellij.net...

>>>> And to make a liar out of myself, the REAL first thing I noticed was
>>>> performance. I expect there's debug and unoptimized code in there, but
>>>> just starting up VS.Net 2003 for the first time took MINUTES and
>>>> MINUTES, with msdev.exe chewing up the CPU. When it FINALLY loaded up,
>>>> it took even longer to load up my relatively modest solution (only
>>>> three projects, but a hundred or so files). MUCH longer than before
>>>> (several times as long).
>>>>
>>>
>>> I did not have the same experience, in fact I find it to be faster that
>>> 1.5. On a solution with 11 projects.
>>
>> Strange. My problem persists. Loading up an empty Visual Studio.Net
>> 2003 takes several times as long as before. Ditto loading up a simple C#
>> solution with three projects and a hundred or so files (only a few of the
>> files are of significant length). It's not just 'noticably' slower.
>> It's many times slower. Still.
>>
>>
>>>> The 'outline brackets' feature was unexpected. I'm going to try it for
>>>> a while to see if I prefer it, or just the coloring of the brackets,
>>>> but it caught me off guard at first.
>>>>
>>>
>>> The outline is ugly, I prefer the coloring.
>>
>> I changed the color of the outline to light-gray from dark-gray, and it's
>> much less offensive. I think I can get used to it and even like it. You
>> might want to give that a try.
>>
>>> I have an issue with Reformat Code, on my base classes it works fine,
>>> but on my child classes I cannot use it, it is grayed out.
>>
>> I haven't noticed this yet, but I'll keep an eye out for it.
>>
>>
>



0
Comment actions Permalink

Sergey V. Coox wrote:

Paul,

Thank You for the feedback. I'll comment some of the point You've.
mentioned.

>>Second thing I noticed was that the lightbulb pop-up is bright magenta. I
>>hope that's not on purpose, and that it's SUPPOSED to be transparent.


Unfortunately, it happens from time to time, but I cannot definitely
reproduce such behavior. In most cases switching to another application and
getting back solves the problem. If You have an idea, how to get this
magenta effect on demand, it will help a lot.

>>And to make a liar out of myself, the REAL first thing I noticed was
>>performance. I expect there's debug and unoptimized code in there, but
>>just starting up VS.Net 2003 for the first time took MINUTES and MINUTES,
>>with msdev.exe chewing up the CPU. When it FINALLY loaded up, it took
>>even longer to load up my relatively modest solution (only three projects,
>>but a hundred or so files). MUCH longer than before (several times as
>>long).


Performance is our main concern. We are working on it.

>>I also noticed the solution opened with the "file structure window" and
>>"test runner window" as these small floating windows, already open. Was
>>that intentional? I really don't think those should default to being
>>displayed like that.


VS tracks the tool windows appearence according to her own strategy, and the
only possible things we are able to do is not to show the windows at the
first start until they are requested to show.

>>And what's "EnableDaemon" (resharper key Ctrl+8)? And maybe it could have
>>a more descriptive name?


This feature toggles file highlighting on/off. Maybe the name is not so good
:)


May I suggest Hector the Inspector? The IDEA EAPers came up with it for
IDEA and the name simply became popular.

--
Rob Harwood
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

PB> First thing I noticed was that the red/yellow/green colors for the
PB> little box have change shades. Just saying I think I prefer the
PB> original shades significantly to these more 'bright' versions.

I prefer the new shades (mellower for me), and I also like the R# logo on
the splashscreen.


0
Comment actions Permalink

I like the new logo on the splash screen, but I really really dislike the
new red/yellow/green shades. They're way too "bright" and draw the eye too
much and I'm finding them just annoying, and they just look "wrong" to me.
It's strange that such a minor issue is one of my biggest complaints right
now, but it is.

I really want them to go back to the original colors.

Or at the very least, let us choose the colors. Because I really hate the
new ones.

"Jean-Francois Heon" <jfheon@yahoo.com> wrote in message
news:6b75b6e54c168c75b26f7022ca6@news.jetbrains.com...

PB> First thing I noticed was that the red/yellow/green colors for the
PB> little box have change shades. Just saying I think I prefer the
PB> original shades significantly to these more 'bright' versions.

>

I prefer the new shades (mellower for me), and I also like the R# logo on
the splashscreen.

>



0
Comment actions Permalink

Good news on the slow start-up issue.

I didn't notice anything during actual use, once the solution was open...
certainly nothing of the magnitude of the slow-downs in start up and
solution opening.

Right now, though, I'm not really looking at performance except when it's so
significant that it actually affects work. I'm more interested in getting
things to work right, and trust that performance issues will be resolved
towards the end of the EAP.

"Eugene Pasynkov (JetBrains)" <Eugene.Pasynkov@jetbrains.com> wrote in
message news:dbl1q6$or1$1@is.intellij.net...

Thank you for the feedback.

>

The GREAT start-up slowdown is the known issue is the major one.
We we deal with it urgently.

>

Did you see any noticable slow-down AFTER the solution is opened? I.e.
in regular work?

>


0
Comment actions Permalink

Unfortunately, it happens from time to time, but I cannot definitely
reproduce such behavior. In most cases switching to another application
and getting back solves the problem. If You have an idea, how to get this
magenta effect on demand, it will help a lot.


If I can reproduce it, I'll let you know. So far, I just experienced it
during the initial run after installation. After that, I haven't seen it
since.

Performance is our main concern. We are working on it.


Excellent.

VS tracks the tool windows appearence according to her own strategy, and
the only possible things we are able to do is not to show the windows at
the first start until they are requested to show.


I would definitely suggest not showing the windows until the user requests
them. I find it annoying to have to constantly be closing them.

>> And what's "EnableDaemon" (resharper key Ctrl+8)? And maybe it could
>> have a more descriptive name?

This feature toggles file highlighting on/off. Maybe the name is not so
good :)


Yeah, the name stinks :) I'd suggest "Toggle syntax highlighting" or
something equally intuitive :)

>> There's also lots of "TOOLzzzXXXzzz" entries in the Resharper key maps,
>> where "XXX" is some legitimate command name.

These are the commands to activate our tool windows. We'll change the
command names.


Okay. That makes sense.

Any word on when we'll first see the "Complete Statement" feature? I think
of all the features I'm looking forward to, I'm looking forward to that one
the most, because it'll affect my work the most.


0
Comment actions Permalink

I've found that my aspx pages loads faster after installing 2.0, not sure
why, but with 1.5 they took ages to load. So in that respect I was very
happy, since I'm working on a large asp.net app at the moment...

"Eugene Pasynkov (JetBrains)" <Eugene.Pasynkov@jetbrains.com> wrote in
message news:dbl1q6$or1$1@is.intellij.net...

Thank you for the feedback.

>

The GREAT start-up slowdown is the known issue is the major one.
We we deal with it urgently.

>

Did you see any noticable slow-down AFTER the solution is opened? I.e.
in regular work?

>

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dbkquo$b9$1@is.intellij.net...

>> Just to quantify the numbers... with Resharper 1.5, loading an empty
>> Visual Studio.Net (just a start page, no solution) takes well under 5
>> seconds from cliking on the launch icon to being ready to work.
>>
>> With Resharper 2.0, it takes a full 60 seconds to get to that point, most
>> of it just staring at the splash screen.
>>
>>
>> "Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
>> news:dbkkvl$dkv$1@is.intellij.net...
>>>>> And to make a liar out of myself, the REAL first thing I noticed was
>>>>> performance. I expect there's debug and unoptimized code in there,
>>>>> but just starting up VS.Net 2003 for the first time took MINUTES and
>>>>> MINUTES, with msdev.exe chewing up the CPU. When it FINALLY loaded
>>>>> up, it took even longer to load up my relatively modest solution (only
>>>>> three projects, but a hundred or so files). MUCH longer than before
>>>>> (several times as long).
>>>>>
>>>>
>>>> I did not have the same experience, in fact I find it to be faster that
>>>> 1.5. On a solution with 11 projects.
>>>
>>> Strange. My problem persists. Loading up an empty Visual Studio.Net
>>> 2003 takes several times as long as before. Ditto loading up a simple
>>> C# solution with three projects and a hundred or so files (only a few of
>>> the files are of significant length). It's not just 'noticably' slower.
>>> It's many times slower. Still.
>>>
>>>
>>>>> The 'outline brackets' feature was unexpected. I'm going to try it
>>>>> for a while to see if I prefer it, or just the coloring of the
>>>>> brackets, but it caught me off guard at first.
>>>>>
>>>>
>>>> The outline is ugly, I prefer the coloring.
>>>
>>> I changed the color of the outline to light-gray from dark-gray, and
>>> it's much less offensive. I think I can get used to it and even like
>>> it. You might want to give that a try.
>>>
>>>> I have an issue with Reformat Code, on my base classes it works fine,
>>>> but on my child classes I cannot use it, it is grayed out.
>>>
>>> I haven't noticed this yet, but I'll keep an eye out for it.
>>>
>>>
>>
>>
>



0
Comment actions Permalink

Any word on when we'll first see the "Complete Statement" feature? I
think of all the features I'm looking forward to, I'm looking forward to
that one the most, because it'll affect my work the most.


This feature is planned by the release, but not yet done :(

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

>I like the new logo on the splash screen, but I really really dislike the
>new red/yellow/green shades. They're way too "bright" and draw the eye too
>much and I'm finding them just annoying, and they just look "wrong" to me.
>It's strange that such a minor issue is one of my biggest complaints right
>now, but it is.

They are already changes to the darker ones.

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I am noticing a slow-down during normal use - mainly that when task-switching
back to VS the resharper 'scanning' progress dialog pops up and takes a few
seconds before going away.

Also,
I use a light-on-dark colour scheme and, firstly, lots of the colour 'names'
have changed on 2.0 so I lost the ones from 1.5 and had to re-do them, comparing
the registry settings for VS they are not that dissimilar in most cases,
but far enough off to make them get lost.
When the light-bulb helpers are shown there is also no transparency (grey
background) so now with my dark background they look like weird circles in
grey boxes!

For some reason, quite regularly base-class functions are not recognised
and marked as 'cannot resolve symbol' - if I rewrite the inheritance line
(public class myclass : baseclass) then upon rescanning it is fine!

There is definately something different about the rescanning of the files
- I guess this is all part of removing the progress bar and doing it all
in the background, but it seems to take longer now - and the addition of
the different icons in the corner showing how far it has got don't really
help - the more pastel colours don't draw your eye to the state as much as
the old bolder colours - can they be customisable?

Thank you for the feedback.

The GREAT start-up slowdown is the known issue is the major one. We we
deal with it urgently.

Did you see any noticable slow-down AFTER the solution is opened?
I.e. in regular work?



0
Comment actions Permalink

My magenta background has NOT gone away after restarting! :(

Hello Paul,

re: the magenta background to the lightbulb... after restarting, it
went away, and looks acceptable. However, the behavior is slightly
weird. The surrounding box and down-arrow only appears when the arrow
is exactly over the image of the bulb. Move the cursor off the bulb,
and the box and the down-arrow disappear... now, given that the
down-arrow looks like something you could or should click on to see
the options, this is bad. In fact, since clicking on the bulb does
exactly what you think it should, I wonder why the box/down-arrow
thing is there at all?

>

]]>


0
Comment actions Permalink

Hello ronnie@freenet.co.uk,

I am noticing a slow-down during normal use - mainly that when
task-switching back to VS the resharper 'scanning' progress dialog
pops up and takes a few seconds before going away.


We are going to do many performance improvements in this area.


Also,
I use a light-on-dark colour scheme and, firstly, lots of the colour 'names'
have changed on 2.0 so I lost the ones from 1.5 and had to re-do them,
comparing the registry settings for VS they are not that dissimilar in most
cases, but far enough off to make them get lost.


We can probably do some color migration during installation. Could you submit
a request inot tracker, please?

When the light-bulb helpers are shown there is also no transparency (grey
background) so now with my dark background they look like weird circles in
grey boxes!


This is a known problem. Solutions are investigated.


There is definately something different about the rescanning of the
files - I guess this is all part of removing the progress bar and
doing it all in the background, but it seems to take longer now


Expect improvements in this area also.

- and the addition of the different icons in the corner showing how far it
has got don't really help - the more pastel colours don't draw your
eye to the state as much as the old bolder colours - can they be
customisable?


We will fix the colors to match the colors of stripes in the next build.

Friendly,
Dmitry
--
Dmitry Lomov
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop With Pleasure!"


0
Comment actions Permalink


"Sergey V. Coox" <qx@intellij.com> wrote in message
news:dbkuu9$e2t$1@is.intellij.net...

Paul,

>

Thank You for the feedback. I'll comment some of the point You've.
mentioned.

>
>> Second thing I noticed was that the lightbulb pop-up is bright magenta.
>> I hope that's not on purpose, and that it's SUPPOSED to be transparent.

Unfortunately, it happens from time to time, but I cannot definitely
reproduce such behavior. In most cases switching to another application
and getting back solves the problem. If You have an idea, how to get this
magenta effect on demand, it will help a lot.

>

Well, in 201, it was magenta at first, but then went normal after... I only
saw it once, really.

Now, in 202, I've restarted a dozen times, but it's still bright magenta,
all the time. I have yet to see a lightbulb without the magenta background.
So now it's always reproducable. Different solutions, different projects,
etc.



0
Comment actions Permalink


--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dc93p1$u9k$1@is.intellij.net...
>

"Sergey V. Coox" <qx@intellij.com> wrote in message
news:dbkuu9$e2t$1@is.intellij.net...

>> Paul,
>>
>> Thank You for the feedback. I'll comment some of the point You've.
>> mentioned.
>>
>>> Second thing I noticed was that the lightbulb pop-up is bright magenta.
>>> I hope that's not on purpose, and that it's SUPPOSED to be transparent.
>> Unfortunately, it happens from time to time, but I cannot definitely
>> reproduce such behavior. In most cases switching to another application
>> and getting back solves the problem. If You have an idea, how to get this
>> magenta effect on demand, it will help a lot.
>>
>

Well, in 201, it was magenta at first, but then went normal after... I
only saw it once, really.

>

Now, in 202, I've restarted a dozen times, but it's still bright magenta,
all the time. I have yet to see a lightbulb without the magenta
background. So now it's always reproducable. Different solutions,
different projects, etc.

>
>



0
Comment actions Permalink

I'm doing everything in VS2003.

"Sergey V. Coox" <qx@intellij.com> wrote in message
news:dca755$rc7$1@is.intellij.net...
>
>

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dc93p1$u9k$1@is.intellij.net...

>>
>> "Sergey V. Coox" <qx@intellij.com> wrote in message
>> news:dbkuu9$e2t$1@is.intellij.net...
>>> Paul,
>>>
>>> Thank You for the feedback. I'll comment some of the point You've.
>>> mentioned.
>>>
>>>> Second thing I noticed was that the lightbulb pop-up is bright magenta.
>>>> I hope that's not on purpose, and that it's SUPPOSED to be transparent.
>>> Unfortunately, it happens from time to time, but I cannot definitely
>>> reproduce such behavior. In most cases switching to another application
>>> and getting back solves the problem. If You have an idea, how to get
>>> this magenta effect on demand, it will help a lot.
>>>
>>
>> Well, in 201, it was magenta at first, but then went normal after... I
>> only saw it once, really.
>>
>> Now, in 202, I've restarted a dozen times, but it's still bright magenta,
>> all the time. I have yet to see a lightbulb without the magenta
>> background. So now it's always reproducable. Different solutions,
>> different projects, etc.
>>
>>
>>
>



0

Please sign in to leave a comment.