New GalleryView Build and a .NET gotcha
A new build of the GalleryView Fiddler Extension has been posted. The new version is 2.1.0.3.
This version fixes an annoying bug: previously, when displaying an animated image, the viewer would throw an exception and display the annoying red X.
It turns out that when an image is loaded from a stream using the Image.FromStream(Stream) method, GDI+ requires the stream to be opened for the lifetime of the image. In the original build, the stream was been closed immediately after assigning the image to the PictureBox so an exception is raised when the PictureBox attempts to animate the image.
This version fixes an annoying bug: previously, when displaying an animated image, the viewer would throw an exception and display the annoying red X.
It turns out that when an image is loaded from a stream using the Image.FromStream(Stream) method, GDI+ requires the stream to be opened for the lifetime of the image. In the original build, the stream was been closed immediately after assigning the image to the PictureBox so an exception is raised when the PictureBox attempts to animate the image.
posted by Ericlaw at
12:47 PM
4 Comments:
Is there a way to download all available extensions in one zip file? If not, can you please add such an option?
Also, the link to SyntaxView2 Inspector download seems to be broken. It links to syntaxview2setup instead of syntaxview2setup.exe.
By
Anonymous, at 9:39 PM
Can you elaborate on why the .ZIP would be preferable? Because the installations are built separately, this would involve additional work for every build on my part, and I'm not sure why this would be desirable.
Thanks-- I fixed the instance of the broken link (the other one worked).
By
Ericlaw, at 11:36 AM
Well, when I come to the extensions page once in a month or so, I might be left behind of updates, and since I trust you that most of the plugins would be useful to me, at least in some cases, I don't want to have to check for each plugin whether I already have it or not, and whether I have the latest version. I just want to make sure I have the most updated version of each extension.
The easiest way to accomplish it is to have one install that installs the latest version of all plugins. However, this is not critical, and if it requires more work on your side, then I guess I can leave without it.
Another option would be for Fiddler to check on startup if new extensions are available or if updates for existing extensions are available, but this might require an option to turn it off, or to not alert me about updates to specific extension which I know I don't want.
By
Anonymous, at 9:16 PM
Thanks for the note, Splintor!
One of the concerns I have is that there are a half-dozen or so more extensions in the pipeline, and many users will not want them all. In some cases, a few of the extensions will require fast procs/lots-of-ram in order to not slow down Fiddler.
I'm nervous about bundling these all together because users might end up with code they don't want, slowing down their experience...
By
Ericlaw, at 7:36 PM
Post a Comment
<< Home