Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>With the first approach, it looks like you're almost there: the only really significant problem is that the repeated calls to UpdateData() mess with the cursor position as the user is typing.</p> <p>Given that you're trying to have a reasonably complex interaction between the controls, what I'd suggest is not to do validation in the OnChange() at all, so that as the user is typing he can type what he wants (which is how most numeric edit controls work anyway). When the user closes the dialog the controls are on (or clicks a button that uses the data in some way) then validation should be triggered, and a suitable error shown.</p> <p>Once you're free from validating in OnChange(), you can fix the "cursor moves" problem by simply not calling UpdateData() in OnChange(). Instead, just parse the number from "editString" and, if it's in the valid range, update the scrollbar. That way, the scrollbar updates as the user types, and if they type in an invalid value the scrollbar stays put, and they'll get an error when they move to whatever the next stage is. Something like this (not tested):</p> <pre><code>void MarginDlg::OnEnChangeFueledit() { CString editString; GetDlgItem(IDC_FUELEDIT)-&gt;GetWindowText(editString); double editValue; if ((sscanf(editString,"%lf",&amp;editValue) == 1) { if (editValue &gt;= 0.0) &amp;&amp; (editValue &lt;= 1.0)) fuelScroll.SetScrollPos(int(editValue*1000)); } } </code></pre> <p>The only remaining important problem to note is that, if the user types some invalid value, or a number out of the valid range, then the edit control and the scrollbar will be out of sync. The simplest way to deal with that is to just decide that the edit control is the "master" value: that is, when we want to know what the user entered, we always look at the edit control, not the scrollbar, and validate data.</p> <p>As for your second approach, one possible solution might be to implement a timer message handler: in the timer handler you could say the equivalent of "if the user hasn't typed anything for a second, I'll assume they're done, and parse the number and update the scrollbar". I'm not so keen on that as a solution, though.</p>
    singulars
    1. This table or related slice is empty.
    1. PO"Smart" Linked Scrollbar and Edit Controls?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDavidK
    1. USDavidK
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO"Smart" Linked Scrollbar and Edit Controls?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI used this method for my onchange and am very pleased with the results. Thanks! I do minimal error checking in killfocus, i.e. make sure the number is in range, and if it's not I set it to either 0 or 1 (and update the scrollbar accordingly). I would LIKE to update my results there as well but I'm having some issues... so I'm currently in the process of debugging that. But thank you very much for your solution.
      singulars
      1. PO
      1. USLauren
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload