Hello Beautiful Looking Code Lovers!
While preparing my next hot update for Script Inspector, version 1.4 I was surprised this morning after opening the Asset Store. The Script Inspector was featured in the big main box at the top of Asset Store Home Page!!! How did this happen? I have no idea, but certainly I have no complains. Awesomeness! Thank you Unity!!! 😀
Well, it was great to see the Script Inspector there, and also to see it featured in the Extensions category. Right now the big box features another great product – 2D Toolkit, while the Script Inspector is still listed on the Home Page in one of those featured products right below the big box. Not bad at all!
So what this all means for those of you who are already using the Script Inspector or consider doing that? Well, this comes as a great motivation for me to work harder on the code editing feature. Very soon I will be releasing a small step in that direction, version 1.4 with full mouse and keyboard cursor navigation inside the Script Inspector and text selecting functionality! No support for editing yet, but there will be only a small step left to get there with the next update, labeled as version 2.0. Well, it might be a little more than just a small step, let’s see.
Finally I would like to thank everyone for the support, great reviews, and comments! Without that I would probably give up from this project long time ago 😉
That’s it for now, gotta finish that update now…
Cheers,
Flipbookee
4 Comments
Add comment Cancel reply
This site uses Akismet to reduce spam. Learn how your comment data is processed.
I couldn’t find a contact email address so I’m writing here. There is a bug with the Script Inspector and I don’t know how to reproduce it but it happens sometimes. I can’t save my script in my IDE, it says “Can’t save the file, it’s being used in another process”. This happened on 3 different computers with both Visual Studio and Monodevelop. I deleted the Script Inspector and it’s working fine now. I won’t be able to use this product as long as this happens, hope you can fix it. Thanks.
Hi there! Thanks a lot for reporting the bug and I’m very sorry for the inconvenience. This bug was found a few days ago and fixed in Script Inspector 1.4 which was published on Asset Store just a couple of days ago. Please update to the latest version and in addition to that bug fix you will be surprised by the amount of new features! Version 1.4 is a transition step to the editing feature (under development right now) and it offers extensive keyboard and mouse support for cursor navigation and selections within the content of the scripts being inspected. This has been the biggest update of the Script Inspector since its launch in May 2012, with the code size being doubled since version 1.0!
Please let me know if this resolves the bug you mentioned. Other than that I hope you really enjoy using the Script Inspector. 🙂 Don’t hesitate to leave your feedback here or as a review in the Asset Store.
It’s good tool.
But i want to use Japanese fonts ‘2 byte code.??,KANJI’. Please.
Thanks Haru!!! 🙂
Sure, I’ll look at that too and I’ll let you know.