LINQPad 9 - Early Preview now available
Comments
-
Part two, the code that linqpad proxying for gpt-4.1-mini didn't like.
-
Thanks for providing that detailed info. It looks like catastrophic backtracking in the regex engine. I've just uploaded an update that avoids regex and is hundreds of times faster. Let me know how you get along.
-
While typing in the latest version of LINQPad, I randomly encounter NREs. Could this be related to IntelliSense failing to initialize?
-
This should be fixed in the latest build. Let me know if it's still an issue.
-
Enjoying the new v9 UI - thank you. Minor feedback that I would put my hand up for would be:
- Tabs: Could script tabs be like "My Scripts" and "Samples" - ie no bottom radius and border?
- Compactness: It looks great on a small screen and vertical space is nicely prioritised. On a larger screen, I'd love to be able to increase the 'air' around panels. Would a user setting named something like 'MarginFactor' (defaults to 1) work? I'm thinking of something akin to the touch mode in Office, although touch is not the motivation for this.
- Margin above first line in editor (void Main())
- Margin above root node in "My Scripts" treeview
- Top and bottom margins of editor toolbar
-
There appears to be a change in how references are managed. Namely, if I have added a normal reference to an assembly and that assembly is updated, LINQPad would have detected the change in the file and refresh the intellisense cache and whatnot.
It doesn't seem to be doing that now. I would have to remove the reference and add it back to see the changes. This breaks my workflow of developing my components in my IDE and run tests in LINQPad. Could this behavior be restored?
-
@JohnGoldsmith - Tabs cannot be changed without a rewrite. This will happen at some stage but is not highest priority right now. Regarding compactness, the old version had a tablet mode and I could reintroduce that. However, your suggestions as to where to increase margin are all reasonable (and some were already on the TODO list) so where I might start is to add a couple of pixels or so in those areas - this may be enough to balance the UI without needing to create a separate option. This should be in the build for late next week. Let me know what you think at that point.
-
That would be great. Will standby for next week.
-
There has been a few changes to completion on missing methods which makes it less helpful.
In the following example, the option I would like (i.e. to replace Image with LINQPad.Controls.Image) is missing in LP9.
Contrast with LP8
Also, I miss the little down arrows at the end of the definition and clicking on the lightbulb sometimes works, but most of the time it seems to briefly display the options menu and then immediately dismisses the menu. It looks to me that I need to click on the left hand side of the lightbulb icon for it to stay open.
-
@JohnGoldsmith - 9.2.12 has now been released with the adjusted margins.
@JeffMercado - I have not been able to reproduce this. Do you have an MRE? Keep in mind that files referenced across network connections or symlinks are not watched.
@sgmoore - Thank you - this has now been fixed in 9.2.12.
-
@JoeAlbahari I'll see about trying to make a repro. I believe it was just a simple netstandard 2.0 (might have been targeting .NET Framework 4.6.1) windows forms library that I wanted to test. And all I did was create an instance of one of the forms and show it.
Made changes to the constructor (added parameters) and trying to run (without changes to the original code) lead to missing method errors I think. No compile time errors or red squigglies until I removed and restored the assembly.
If there are no changes to any of the used methods or properties after updating and is source compatible, it'll run ok, and I can see the updated form.
The script will pick up the updated assembly when run, but the intellisense did not get the update and still thinks the assembly is a previous version.
I'll have to check back with you when I get back to the office. I can't reproduce either with a basic example. The project I was working on and its dependencies were... complicated. I was adding a reference to assemblies that were placed within Program Files so there might be some permissions complications maybe.
-
Thanks @JoeAlbahari I think if this were a setting then I would go even further. On my large screen vertical space isn't an issue at all and so I'd go for even more separation
