| T O P I C R E V I E W |
| mparker |
Posted - Jan 08 2025 : 1:37:35 PM
After updating to 2547 in VS 17.12.3, I no longer get Enhanced Syntax Coloring in the Find in Files results window. I have all boxes in Options -> Coloring and Attributes -> "Apply coloring to" checked. Sometimes after a Find, some broken-looking portion of the first line is colorized, but the rest are all just white on black (dark theme). I can't reliably repro that, so I don't have a screenshot to share. I make use of this colorization constantly to make the Find operation more useful, so I noticed right away when it was gone. Let me know if there's any more info you need for a repro, hopefully it happens for you right away and is not just me. |
| 14 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Apr 10 2025 : 06:24:37 AM
Personally I do tend to agree with you, but only tend to. The reason is that some of the problems we get with VA are caused by changed in Visual Studio, which we then have to work to adapt to. Features in VA can go from working to not working, even though VA hasn't changed at all. Yet from the point of view of a user of VA, its a "regression". Happy to accept I am splitting hairs here, but from a technical point of view, there is an important difference here.
The second reason is the, thankfully very small, number of crash or other deeply serious problems that crop up. These have to take priority.
Having said all of this, I really do see and appreciate your point, and this is down as an urgent bug fix we need to get sorted. |
| SvenR |
Posted - Apr 10 2025 : 04:57:36 AM
In my work, regressions are always more important than new features. After all, what use is a new feature to the user if a regression prevents him from using it? This is especially important when software is offered with a subscription.
A good example of this is 'Ray lines' from VA 2547. I would love to use it, but I'm stuck with this regression at 2537. My subscription runs from June to June. So I pay for 12 months, but so far I've only been able to enjoy new features for four months. The developers should also keep this in mind when prioritizing work items. |
| feline |
Posted - Apr 09 2025 : 08:08:42 AM
I always put in bug reports for regressions as high priority, since breaking anything that was working is definitely a "bad thing". But we also have to prioritise adding new features and general bug fixes, especially for high priority and serious bugs. It's a balancing act, as always. |
| SvenR |
Posted - Apr 09 2025 : 05:36:19 AM
Thank you, feline. In my humble opinion, fixing regressions should be the top priority. Ideally with a hotfix, but at least with the next regular update. |
| feline |
Posted - Apr 08 2025 : 08:21:09 AM
OK, there are two separate cases here. Firstly we have:
case=165395
which covers putting the IDE find results window back into list view mode. VA colouring used to work here, and got broken. This is down as a fairly urgent bug fix, which we are hoping to get to soon, but I don't currently have a proper estimate yet. But this is something we are looking at. For now all I can do is apologise for the breaking of this feature, and reassure you that it is something we are aware of, and looking to get fixed soon.
The second case is:
case=141315
which is a feature request to apply syntax colouring to the IDE find results window when it is in tree mode. This is still in the being considered pile, so no estimate yet on this, but I suspect it will be done eventually. |
| SvenR |
Posted - Apr 08 2025 : 01:27:47 AM
Me too. I'm still on 2537 because I'm used to the syntax highlighting in the search results list. If I pay for updates every year, then I want to use the latest version without any restrictions to the functionality I'm used to. |
| mparker |
Posted - Apr 04 2025 : 5:37:48 PM
quote:
Originally posted by feline
Now I know to use the List View button, the problem is quite clear, and definitely a regression.
I have put in a bug report for this:
case=165395
I was disappointed to see 2554 didn't fix this. I realize the team has their own priorities, but this was one of the highest ones for me. Do you think a fix will be forthcoming in the next release? Honestly, I already dread waiting that long without this feature. :/ |
| feline |
Posted - Jan 31 2025 : 09:52:59 AM
We are considering colouring the Find results in tree view, but its not currently an immediate idea, just something we are aware of:
case=141315 |
| Dan Forever |
Posted - Jan 31 2025 : 03:39:04 AM
I also experience this problem (for what it's worth).
Since the introduction of the tree view, I also immediately switched back to the list view, and the reason I did this was because there is/was no VAX highlighting on the tree view (but the list view still had the same syntax colouring as always).
I may consider using the tree view search results in future should VAX colouring be added to it :D |
| mparker |
Posted - Jan 10 2025 : 12:36:26 PM
Thanks for that. The list view was the only view until fairly recently, and I switched back to it when the tree view came out, so I forgot there were options. Thanks to tomob for pointing that out. |
| feline |
Posted - Jan 10 2025 : 11:38:26 AM
Apologies, I didn't notice the "List View" button, so thought that VS2019 and VS2022 only had the tree control version of the find in files results. I don't spend a lot of time with this results window.
Now I know to use the List View button, the problem is quite clear, and definitely a regression.
I have put in a bug report for this:
case=165395 |
| tomob |
Posted - Jan 10 2025 : 03:36:04 AM
I would like to confirm that I have the same issue after upgrading to 2547. In all previous versions in order to have coloring enabled in Find Results one had to have the Views in Coloring and Attributes checked and the Find Results pane needed to have the List View option enabled. Now after the upgrade this doesn't work, but sometimes I see random coloring there. |
| mparker |
Posted - Jan 09 2025 : 12:06:41 PM
I'm afraid I must disagree. I have screenshots from 2537 (working) and 2547 (not working) that I've captured just now. If it's truly not coloring the text in the window, and some other VS feature is causing it to be colorized using VA colors, then 2547 is now preventing whatever that is from working. It has colorized that window for... time is difficult, but I want to say "years". Maybe it's not as long as I'm imagining, but I rely on that many times every day.
To be on the safe side, I should probably email the screenshots rather than attaching them here. Can you send me a DM with where is best to send those? |
| feline |
Posted - Jan 09 2025 : 05:37:15 AM
VA doesn't try to colour the IDE Find in Files results window. I have just double checked VS2022, VS2019 and VS2017 to make sure. Were you expecting to see VA colouring here?
Or are you talking about VA's Find References Results window? |
