The native Rich Edit control will not tell you whether the next character keyed will be inserted or overwritten. You will have to trap keystrokes and track the insert/overwrite mode yourself. One way to do this is to write your own class, presumably derived from TRichEdit, to track the control's current insert/overwrite state. Note that Rich Edit controls are in insert mode when created.

First, a brief description of the problem: Assume that you are writing a chat room program. As new messages are a posted in the chat room, you want to append them to the text in the control. However, to do this, you must position the caret at the bottom of the text and then insert the text. Finally, you need to restore the original caret position (easy) and scroll back such that the top line displayed is the same one as before inserting the text (not so easy).

You can handle the textbox's KeyPress event and if you want the keypress to be an overwrite, just select the current character so the keypress will replace it. The attached sample has a derived textbox that has an OverWrite property and a right-click...

When recording is completed, the dictation audio can be reviewed in real-time. Options like insert, overwrite, append, fast forward, rewind and pause become available. These options can be configured to be activated by any touch-tone key.

You can set the default SQL mode (for mysqld startup) with the --sql-mode option. Using the statement SET [SESSION|GLOBAL] sql_mode='modes', you can change the settings from within a connection, either locally to the connection, or to take effect globally. You can retrieve the current mode by issuing a SELECT @@sql_mode statement.

Remy Lebeau (Gambit) offered the following solution in a C++ Builder forum. Simply publish the unpublished OnDblClick event like so: class PACKAGE TMyRichEdit : public TRichEdit { public: __fastcall TMyRichEdit(TComponent* Owner); __published: __property OnDblClick; }; __fastcall TMyRichEdit::TMyRichEdit(TComponent* Owner) : TRichEdit(Owner) { } void __fastcall TForm1::MyRichEditDblClick(TObject* Sender) { ShowMessage("double-clicked"); }

Overwrite will overwrite a previously recorded file from any point within the file. Insert recording will insert voice recordings into previously recorded file.

Press Ctrl-L to refresh the screen. It didn't actually overwrite the message text but it sure is confusing.

Since this is illegal, also in Clipper ;-) The display should/need to be handled by the GET object itself. In textual mode, which has only one screen layer = the screen buffer self, you of course can override this HW buffer and hence "tricking" the object display.

Not by default, but you can change the tkTextInsert and tkEntryInsert library procedures to include this with the following: proc tkTextInsert {w s} { global tkPriv if {[string match {} $s] || [string match "disabled" [$w cget -state]])} { return } if {[catch { if {[$w compare sel.first <= insert] && [$w compare sel.last >= insert]} { $w delete sel.first sel.

Use the OCX component to find out who is logged in, http://www.flicks.com/authentix/currentusername.htm You should be able to add the component to your cgi or asp program, or you can get it out of HTTP_AUTHORIZATION and then base64 decode it. Note that if NTCR (Integrated Windows Authentication in Windows 2000) is turned on, then CurrentUserName may not return the expected result. See the documentation to find the cause and workaround.

I do not know of a way to do this with Rich Edit 1.0 controls. Kimberly says that it cannot be done: "As it ends up, RE 1.0 doesn't support transparent background. It paints the background in the WM_PAINT message instead of the WM_ERASEBKGND." Kimberly went on to point out that Rich Edit 2.0 controls can be created with the WS_EX_TRANSPARENT style to allow a background bitmap to show through.

This appears to be a bug in the Rich Edit control or in the TRichEdit class. I have found some magical code in TRichEdit (meaning that I have not bothered to completely debug it) that may be responsible. Anyway, here is a workaround (along with my comments to myself): // apparently there is a bug which we must work around... if you drop a large // file (> 32k?) on a TRichEdit, the vertical scroll bar is not enabled until the // control is manually scrolled down a page.

To scroll to the bottom of the text in the component, move the selection to the bottom and then tell the TRichEdit to scroll to the caret like so: RichEdit1->SelLength = 0; RichEdit1->SelStart = RichEdit1->GetTextLen(); ::SendMessage(RichEdit1->Handle, EM_SCROLLCARET, 0, 0); If that does not work, you may need to add code to ensure that the Rich Edit control has focus.

If you're running SP1 or later you can do it with Insert | Date & Time or by pressing ALT+SHIFT+F

It is sometimes called a base-page. It is the foundation of the album and is attached to the binding of the cover by pins, hinges, clips and stitching.

Different integration modes allow you to integrate 'Step by Step' FileUploader Control into your existed Application. Simple - http-module is disabled, Mediachase.FileUploader.Web.UI.McHtmlFileInput control elements are used Medium - http-module is activated, Mediachase.FileUploader.Web.UI.McHtmlFileInput control elements are used, large file optimization is not used Full - http-module is activated, Mediachase.FileUploader.Web.UI.

Two reasons. The first is that the current protocol tends to produce very short insert size or even overlaped two ends. The second reason is due to the algorithm used by Maq. Without setting minimum insert size helps to get slightly better, though a bit more conservative, alignment.

The maximum allowable capacitor RMS current varies as a function of operating frequency, assuming there is a constant RMS peak working voltage. Standard derating curves are published in our catalog. A complete response to this question can be found in the Jennings TechNote C-3: "The Effects of Current on Vacuum Capacitors" Yes, the torque required to change capacitance values does change over time. The changes in torque will appear randomly and are not directly related to time or capacitor age.