Utilities Script Inspector 3

Hi, I have a question. Is there any ETA of the curly brackets code folding feature? I guess it woudn't differ much from region folding functionality.

 

Yes, it wouldn't differ much — that's low-hanging fruit.

I can't say when it might be done before trying to do that. I thought auto-implementing interfaces would be easy, but no, I'm still working on it, and I didn't know that before starting to work on it. So I can only say that I'll try that next, and if nothing surprises me, it will be done quickly.

 

Don't add unit testing to your code! It may reveal swarms of bugs, which will delay your release date.

That's my sarcastic excuse for delaying the next update for Si3
Bear with me, please...

 

Hey small Q
any updates on this?
i am still on pop os, and well, issue is still here

 

I made some progress last week, but let me check in what state it's now, and I'll send you a copy

 

I have a long list of unreleased fixes. What do you guys think? Shall I release these now and continue working on finishing the new features?

 

Do it ! and then you can work on the rest after that

 

Right, it's much easier to work without all the pressure from unreleased fixes... Releasing the pressure now
______________


Hey, my friends! I know you're all enjoying working in Unity like never before, thanks to Si3, of course, even though you might have encountered some tiny bugs. As someone who's spent his whole life coding, I know how annoying even the most minor bugs in the code editor can be. But worry not; I'm here for you to help fix that while you can focus on your code.

Script Inspector 3
version 3.1.7
is available on the Asset Store
​

This is what's new in this release:
- Added support for the dynamic type - thanks @Alaadel
- Made the status label about Hot Reload non-green - thanks @Lars-Steenhoff
- Workaround for a keyboard input bug in Unity Editor running on SteamDeck - thanks @fahrulgamemaker
- Ctrl+S for Save, Ctrl+Z for Undo, and Shift+Ctrl+Z or Ctrl+Y for Redo on Linux - thanks @GrassWhooper
- Fixed Monaco font in Unity 2023.2+ - thanks @ch1ky3n
- Fixed using directives to nested namespaces - thanks @Alaadel
- Fixed tooltips for extension methods with one parameter
- Fixed positioning of the squiggly underline for missing tokens
- Fixed resolving to internal extension methods
- Fixed method overloads resolution with lambda expression arguments
- Fixed method type parameters inference from method group arguments
- Fixed resolving method type parameters in its return type
- Fixed explicit tuple deconstruction of the iterator variable in foreach statements
- Fixed the missing constructor and Invoke method for some delegate types
- Fixed common type inference from array initializer lists
- Fixed type inference for some conditional expressions
- Fixed type of lifted comparison operators
- Fixed using alias directives for namespaces
- Fixed C# parser for initially empty scripts
- Fixed a rare stack overflow exception

Enjoy all these fixes while I'm finishing some new features and improvements.

 

Well, I had to do another minor fix for the text in tooltips in Unity 2023.2+ ¯\_(ツ)_/¯

Please update again to the latest version 3.1.7f (@Lars-Steenhoff, sorry for the double-download).

 

Still have to get around testing it! Thanks for the many fixes

 

My new unit testing is merciless and so brutal. About two weeks ago, I ran it on a larger code base and it found 999+ (that’s the counter limit in the Console) errors. After a week of debugging and fixing mostly tiny bugs, 5 per day in average, I brought that number below 999. Another week of intense bug hunting since then, and now it reports about 70, which are actually 4 distinct issues while the rest are just consequences of those.

So yeah, there will be another release next week after testing these fixes and listing them all as release notes. There are so many fixes this time that I think I’ll have to spend a full day just listing them.

 

Hey, small issue, so i wrote this code
and i noticed, that, the m_x(23.0);
does not get highlighted in red, which i assume is a bug?
not sure if it is to be implemented in future or, if its a bug but i thought i'd mention it.

 

hey again,
sorry for the trouble, but another bug i came across



so, col2d is just a public Collider2D variable
the "ClosestPoint" function, shows hints of the bounds constructor, rather than the variable that the "ClosestPoint" accepts

 

Thanks @GrassWhooper for reporting both issues!

I knew about the first one, but the second one is more interesting for me because it is something I’ve never seen. I’ll check both right now.

 

sorry for trouble, but one more tiny, issue
i noticed that the "Go To Definition" in windows uses F12, which works perfectly.
But, in Linux, it uses F.
and, while that hotkey itself is fine, but imagine the scenario where i am writing code, and like, i need to go to definition, when i press F it will essentially write in code (which is the expected behavior).
would it be alright if you could remap it to F12 just like windows too? or find some alternative way if it makes sense?

 

F? Just the letter F? How did I do that? I'll fix it, thanks @GrassWhooper!

 

I have a request, when I press save, the position of view in the script always jumps to the top. It would be great if it could stay in the place where I was editing the script before I pressed save.

 

That’s something I broke recently. It used to work like that, so yes, I’ll fix that.

 

Actually, no. Unity broke that, it seems, and I still can't figure out how to fix it...

 

Ah bad unity, they tent to break things in LTS, I hope unity will fix it, I guess going back to an older version of sI3 won’t help right?

 

What flavor of Linux is that and what Unity version? F and F12 work fine on my Linux Mint and Unity 2022.3.23f1.

 

Hmm, I haven't tried older versions of Si3. Maybe I should...

I still have no solution for this issue, but I'm still trying different workarounds.

 

its pop us 22.04, which is built upon ubuntu 22.04, and it uses gnome as the desktop environment.
i use unity 2022.3.11f1

thanks for investigating

 

Salutations!

I've been having crashes (a "hold on busy" that last forever) due to FGCodewindow.repaint for a while now on Unity 2022.3.17 and 2022.3.31. The only option is to force close Unity via the task manager.

In all cases, I notice that it is happening when I am using script inspector 3.

Has anyone encountered this issue as well? Is there any way to prevent it from happening?

Thanks!

 

Thanks so much for reporting this!

I'm preparing a new version of Si3 with an unbelievable number of fixes, some of which might have already fixed that issue too. Could you test that? I'll send you a copy right now.

How often does this happen? Can you reproduce it easily?

 

Using Unity 2022.3.31f

I found a bug with this setup :

Code (CSharp):

1. public interface ITest
2. {
3.     void Test();
4. }
5.  
6. public class TestMe : ITest
7. {
8.     string strValue;
9.     int intValue;
10.  
11.     public TestMe(string strValue,int intValue)
12.     {
13.         this.strValue = strValue;
14.         this.intValue = intValue;
15.     }
16.  
17.     public void Test()
18.     {
19.      
20.     }
21. }
22. public class Test : MonoBehaviour
23. {
24.     ITest test;
25.  
26.     void Start()
27.     {
28.         test = new TestMe("test",32); // parameter helper does not shows up
29.     }
30. }

Does anyone experience similar thing ?

 

Thanks @ch1ky3n!

I believe I've fixed that already for the next release. I'll send you a copy, please check

 

Awesome, it works like charm !

 

Well, I installed Pop!_OS 22.04 LTS and Unity 2022.3.11 and I cannot reproduce that. F12 goes to definition and F just inserts the letter F in the code.

I don’t know what else to do now, so I thought it might be best to ask you to try Si3 in a new empty project and check if F works there as it should. I’m suspecting there is something in your Unity project that breaks it, so this would show us if that’s the case or not…