In Far Manager 1.70 you could browse folders with mouse wheel. Rotating wheel would scroll up and down. Middle-click would open a folder. But version 2.0 disables middle-click. Boo! Never take away features from users.
Fortunately it’s very easy to restore this functionality:
- Launch [C:\Program Files\Far2\Addons\Macros\MiddleClickAsEnter.reg]. If you don’t have this folder re-install Far and add Addons Â» Macros feature.
- Restart Far Manager.
Freshly installed Far Manager looks um… small:
Here’s how to make its window bigger:
- Right-click on the window title, select Properties
- Switch to Font tab
- Select a bigger font. I prefer raster font 10 x 18.
- (optional) Switch to Layout tab and change window size there. I leave it as 80 x 25.
Sometimes I need to do something with file that Far Manager can’t help me with. Good example is changing file permissions. In these cases Windows Explorer context menu comes handy:
If you want context menu in Far Manager you need EMenu plugin. Fortunately, it is included with Far by default. Here’s how to set it up:
- Execute [C:\Program Files\Far\Plugins\EMenu\Hotkey.reg]
- Restart Far Manager
- Open Options menu, then Plugins configuration. Select EMenu in the list.
- Uncheck “Show message after execution”.
Now Menu key should invoke context menu. Nice trick is to select Send To – Mail Recipient to quickly open new email with the file attached.
Have you ever encountered this error:
Invalid postback or callback argument. Â Event validation is enabled using <pages enableEventValidation=”true”/> in configuration or <%@ Page EnableEventValidation=”true” %> in a page. Â For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. Â If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.
First, let’s reproduce the problem. Create a new website and copy/paste this code:
<asp:DropDownList ID="dd" runat="server">
<asp:Button ID="Button1" runat="server" Text="Test" />
$("#<%= dd.ClientID %>").append($("<option />")
If you select option “Three” sure enough, exception is thrown. To prevent it you need to supply all possible values for drop-down control:
protected override void Render(HtmlTextWriter writer)
// and so on
The exception is fixed but server variable for drop-down control is useless – it has no idea that you’ve added new item so dd.SelectedValue will give One, not 3. You need to read POST variable directly instead, like this:
protected void Page_Load(object sender, EventArgs e)