Welcome to Geekdojo Sign in | Join | Help

Do you routinely open new folders directly, either because you created one on your desktop, through a shortcut, or by using the new context menu in Visual Studio to explore the folders in your solution? Are you constantly adjusting the size of the Explorer windows because they are too large or too small for your tastes? Do you wonder why Vista does not just remember and open all windows at the same size?

Vista stores settings such as size, location, sort type, icon type, etc… for individual folders you open. Some of these settings can be replicated to other folders using Folder Options / View / Apply to Folders, but that method is not very reliable and no longer applies to all folders as it did in previous versions of Windows.  Vista can still later decide that your documents folder is suddenly a music folder, or your apps folder full of only executables is now a picture folder.

There are some registry settings you can apply that will take care of most of theses issues, except window sizes. I first discovered the settings through a link in the comments on Scott Hanselman's post about Vista’s erratic file type views. Later, after I purchased a new laptop I came across a better explanation on the My Digital Life blog. If you are looking for a way to fix this behavior, I would suggest going there first as this fix is an expanded version of it and requires those steps. Come back here before you open any new windows though. Go ahead… I’ll keep myself busy.

Ok, now that you have completed those steps, we can get that pesky window size issue fixed.

First, right click on your desktop and choose New / Folder.

Next, double click the new folder and drag it out or in to your preferred size. You can also set other properties of the window you want to be the default at this point. For instance, I like by default window view to be details view grouped by the type of item. The folder is empty so you will not see any sorting or grouping, but it will be saved.

Close the window and open the registry editor, type regedit.exe in the quick search bar of the start menu.

Important, The next steps involve editing your registry. The standard disclaimer applies. You can cause serious problems if you are not careful in the registry. Follow these steps though and your computer will survive.

Navigate back to the registry key:

[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\.

You should see a single numbered key under the Bags key. That key represents the settings for the folder you just closed. Open the ‘Shell’ key beneath it and you should see another key with a guid name such as ‘{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7}’. The numbers may be different on your system.

Right click the guid key and choose export. Save the file to your desktop. Use any name you like.

Now that you have a new registry settings file on your desktop, right click the file and choose Edit. You need to make a single change. The second line in the file will be the path in the registry, it will look like:

[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\4\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7}]. 

The piece that needs to be changed is the number after the ‘Bags’ key. In this case it is 4, but your file may be different. Change the number to ‘AllFolders’ so that the line looks like:

[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\AllFolders\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7}].

Save and close the registry settings file. Now to get these settings back into the registry, double click the file and choose ok at the prompt.

Open any folder on your computer and it will look exactly like your first folder. You will need to reset any special folder views you had, such as picture folders. You can do that in two ways. Click the ‘Views’ button at the top of any window or right click in a window and choose ‘Customize This Folder’. Once you have made your change, close the window and Windows will remember the setting for that folder.

2 Comments
Filed Under:

My company Neudesic will once again be hosting NuCon, a deep dive conference into .Net 3.5 and Visual Studio 2008 including LINQ, ADO.Net 3.5, Silverlight and TFS. Microsoft's new IO model (Infrastructure Optimization) will also be covered in one of the tracks.

This year the conferences will take place in Chicago, New York, and Denver starting on February 7th in Chicago.

Space is limited. Get more info and sign up at the NuCon 08 conference site.

 

0 Comments
Filed Under:

Sorry for the delay for all those asking when it would be back up.

If you have any suggestions or bugs please post them to the CodePlex Issue Tracker.

2 Comments
Filed Under:

It joins it’s offspring on CodePlex. At this time only the source is available. The application is still available on the Cropper page here on the dojo.

The comments page here is getting pretty long and it is not a very effective way to track requests and bugs. If you have a request or bug, please post then in the issue tracker on CodePlex

>>Cropper CodePlex Page

 
[Update] CodePlex had issues and the source code for projects on server 3 was lost. Looks like they are trying to recover the data (the work items are back now) but who knows if they will be able to. I don't know what to say about this much TFS hosted source code being lost.
 
If the source code is not back soon I will do another baseline check-in. I just hoped a restore doesn't happen and overwrites that check-in. Sounds like a big mess.

There has been some recent feedback on Cropper requesting a 64 bit compiled version. The current version crashes on 64–bit machines. I do not have handy access to a 64–bit machine right now to test with. If anyone would like to test drive a 64–bit version, please contact me. I will send out a download link.

Request 64–Bit Beta

John Galloway has set up a CodePlex project for Cropper plug-ins. He has an initial release of four plug-ins available including the return of an AVI capture plug-in.

The developer documentation on the plug-in interfaces is nearly complete. I have contacted John so hopefully I can get the documentation completed and up on the project this weekend.

Many readers have asked about the release of the source code for this version. I plan on releasing the source at the same time as the documentation.

After a long break I’m back working on Cropper. I’ve been a bit under the weather lately so I used my free time to get a little work done on it.

Thanks to Jon Galloway for some suggestions and testing the new plug-in functionality. Also to Scott Isaacs for the predefined sizes suggestion and testing.

This release adds new plug-in functionality to allow plug-ins to be configured within the options dialog and have the settings easily persisted into the Cropper configuration file. You can see the new functionality in the Jpeg and Clipboard formats in the Plug-Ins tab of the options dialog. Developer documentation on the new plug-in functionality will come soon.

[Update] There was a rendering bug on systems that do not have themes enabled. Thanks Corey for bringing it to my attention. The download link points to the bug fix version.

>>More info and download

 

Release Notes

1) .Net Framework 2.0. Cropper is now compiled against the .net 2.0 Framework and the installer works on systems with only the 2.0 Framework installed.

2) Vista Compatibility. A new option to hide the form during a screenshot is available in the options dialog. The new option allows Cropper to capture other transparent windows and keeps the crop form from showing up in the capture on Vista Glass. This option is automatically enable when running on Vista but may be overridden by the user.

The Alt+PrintScreen capturing now properly captures windows in Vista that have glass in the client area. 

3) Predefined Sizes. Frequently used form sizes can now be saved. The sizes are managed in the options dialog under the appearance tab. While working with cropper the sizes may be accessed via the right click menu or by pressing Shift+Tab to cycle through the different sizes.

4) Alt+PrintScreen Captures Stay on Clipboard. The Options dialog Capturing tab allows the user to keep Croppers Alt+PrintScreen captures on the clipboard.

5) Configurable Plug-In Support. Cropper now has support for integrated plug-in configuration. A new tab named Plug-Ins will present options from plug-ins that support configuration. The new functionality also supports easily persisting a plug-in's settings into Croppers configuration file.

Two included plug-ins support the new configuration options. The clipboard plug-in allows the user to choose the format of the image that is placed on the clipboard and the Jpeg plug-in has a single option for specifying the file extension. More community plug-ins with configuration support are on the way.

6) 'Prompt' File Name Template Bug Fixed. There was a bug that could cause a null reference exception when using the 'Prompt' file name template that has been fixed. Another bug with the dialog placement when the crop form was set to always on top has also been corrected. 

John Galloway has created a nice animated gif plug-in for Cropper. It has some nice optimizations like a neural net quantizer and capture comparison that only adds a new image if it has changed from the previous one.

You can read more about it on his blog post.

... when strings are so flexible.

Seen all over some production code.

string isValid = SomeDbFunction() == "" ? "T" : "F";
...
if(isValid == "T")
{
    ...
}

// The best part
if(isValid != "F")
{
    ...
}

Patrick updated his Flickr plug-in to 1.8 a couple weeks ago with a bug fix and compilation against the newest Flickr API and I accidentally deleted his trackback while trimming spam.

Look for the update at the bottom of the post.

I am now working on the next version of Cropper. It is still a couple weeks from release but I thought I would release the visualizer I created and have been using during development. The next version of Cropper has the effect plug-ins I mentioned a while back plus support for transparency in non-rectangular form captures and effects.

I needed a visualizer to easily watch the effects as they are applied. Since Cropper will support transparency in the non-client areas of forms and in effects such as drop shadows, I needed the visualizer to indicate the transparent areas of the capture. This visualizer has the standard checkerboard pattern to distinguish the transparent areas of a capture from areas that could otherwise be the same color as the background.  


Bitmap Image Debugger Visualizer Form

Download assembly and source

I can not believe this still happens. VS 2005 with no addins, no other apps running that would access the assembly and requiring a complete shutdown of VS to free the file. Third time this week.

[UPDATE] This only seems to happen when my WinForm project is in the solution. I have a couple class libraries with custom controls and a WinForm app to test them with. The custom controls are added to the WinForm by dragging from the toolbox area that lists the components in the solution. The references to the class libraries are added by Visual Studio when the controls are dropped on the form.

The strange thing is that I can go for a couple hours without getting the error. After the first error that forces me to restart Visual Studio, I get the error again on the second build after each restart. The assembly is getting locked during or after the first build.

The development of my custom controls has become:
            code - build - code - build error - restart - repeat

New Features and bug fixes

1) Per pixel alpha blending. Cropper now uses per pixel alpha blending to render the main window. The size tabs, text and lines have a higher alpha value. This makes the form indicators easier to see at lower opacity levels. The main form area's opacity is still adjustable. On slower machines the crop form may respond slower, in that case you may turn off per pixel alpha blending on the Appearance tab of the options dialog.

Cropper UI

2) More settings persisted. Always on top and hidden settings are now saved between sessions. Cropper will now start minimized the first time it is run on a computer. Thumbnails enabled and the thumbnail indicator showing is also saved between sessions.

3) Print Screen captures. You can now use the Print Screen button to take screen shots with Cropper. The crop form can be minimized. The images will be saved with the same options as regular screen shots. Print Screen will capture and save the entire desktop. Alt + Print Screen will capture the current active window. Ctrl + Alt + Print Screen will capture the region below the mouse. Enable and disable this feature in the options dialog.

Cropper 1.8 Options

4) Transparent window area fill. When using Alt + Print Screen, the transparent areas of the foreground window are filled with the color of your choice. This option will give you clean edges around the non–rectangular areas of a window as in the XP window above and the media player below. The capture is also cropped to the smallest rectangle that will include the visible areas of the form. Enable and disable this feature in the options dialog.

No Fill Capture
No Fill Capture

White Fill Capture
White Fill Capture

Black Fill Capture
Black Fill Capture

5) Portable Cropper. If you run cropper from a thumb drive you can add a file named cropper.portable to the application directory. If Cropper detects this file, it will save the configuration in the application directory and will default to a sub directory named 'Cropper Captures' for the images.

6) New window color. Added a blue window color that is more visible across light and dark backgrounds. I also think it looks nicer. The Tab key now cycles through the three color states.

7) S key captures. The S keys initiates a crop form capture in addition to the Enter key and double clicking.

8) Mouse wheel sizing. The mouse wheel now sizes the form out from the center in addition to the [ and ] keys.

9) The opacity setting is now located in the options dialog. There is also an option to restore it to the menu if you prefer.

10) The menu has been rearranged. Since it has grown it seemed to loose any sense of grouping. I tried to add a more logical layout to it.

11) The Escape key now hides the form instead of closing it.

12) Fixed a bug where the incorrect small icon and application name showed in alternative Alt-Tab applications like TaskSwithXP.

13) Fixed a bug introduced in version 1.7.1 that could cause high CPU usage in some cases.

More info and download >>

18 Comments
Filed Under:

There is suddenly a large international interest in Cropper. I have gotten a number of emails requesting it in other languages. Thankfully most of the strings are already in a resource file. I just need to finish moving a few stragglers I found.

If you would like to help let me know, I'll send you the string file for conversion and give credit on the site and in the app.

Thanks

14 Comments
Filed Under:

Version 1.7.1

[Changes from 1.7]

Fixed a bug when trying to browse the output folder before it was created..

Made changes to the way the resize keys [ and ]  are handled to better support international keyboards.

Added new file name templates for User, Domain, Machine, and Prompt. The prompt template will prompt the user for the text to insert. Users are able to specify folders on the fly this way by entering text such as MegaApp\OptionsDialog. A Default option was also added to the template menu that will set the entire template to the default value.

More info and download >

More Posts Next page »