Add roaster capacity checks to new batch window on profile load

config/Windows/newbatch.xml

             </layout>
             <layout type="horizontal">
                 <label>Roasted Weight:</label>
-                <line id="roast" validator="numeric" />
+                <line id="roast" validator="numeric">0.0</line>
                 <label>Weight Loss:</label>
                 <line id="wloss" writable="false" />
                 <button type="check" id="approval" name="Approved" />
                 roastestimate.text = "";
                 query = query.invalidate();
             });
+            var validateCapacity = function() {
+                if(checkCapacity == "true") {
+                    if(convertToPounds(parseFloat(green.text), unitBox.currentText) > poundsCapacity) {
+                        return false;
+                    }
+                }
+                return true;
+            }
             profilebutton.clicked.connect(function() {
+                var proceed = false;
+                if(validateCapacity()) {
+                    proceed = true;
+                } else {
+                    proceed = displayWarning("Suspicious Input", "Entered green coffee weight exceeds maximum batch size. Continue?");
+                }
+                if(proceed) {
+                    doLoadProfile();
+                }
+            });
+            var doLoadProfile = function() {
                 batch.windowModified = true;
                 currentBatchInfo = batch;
                 query = new QSqlQuery();
                 log.updatesEnabled = true;
                 graph.updatesEnabled = true;
                 log.newAnnotation("End", 1, lc);
-            });
+            }
             var noprofilebutton = findChildObject(this, 'noprofile');
             noprofilebutton.clicked.connect(function() {
                 batch.windowModified = true;

src/typica.w

     return QScriptValue();
 }
 
+@* Scripting QMessageBox.
+
+\noindent Some features require that \pn{} pauses an operation until further
+information can be obtained. An example of this is discretionary validation
+where input is checked and if it seems unlikely but not impossible to be
+correct a dialog should come up asking if that input is correct. If it is not,
+the operation should be cancelled and the person using \pn{} should be allowed
+to correct the information and try again.
+
+For this use case, it is not necessary to fully expose the |QMessageBox| class.
+Instead, it is enough to provide a function that will raise an appropriate
+message and return the selected action.
+
+@<Function prototypes for scripting@>=
+QScriptValue displayWarning(QScriptContext *context, QScriptEngine *engine);
+
+@ This function is exposed to the host environment.
+
+@<Set up the scripting engine@>=
+constructor = engine->newFunction(displayWarning);
+engine->globalObject().setProperty("displayWarning", constructor);
+
+@ The function takes some arguments.
+
+@<Functions for scripting@>=
+QScriptValue displayWarning(QScriptContext *context, QScriptEngine *)
+{
+    QMessageBox::StandardButton selection = QMessageBox::warning(NULL,
+        argument<QString>(0, context),
+        argument<QString>(1, context),
+        QMessageBox::Ok | QMessageBox::Cancel);
+    if(selection == QMessageBox::Ok) {
+        return QScriptValue(true);
+    }
+    return QScriptValue(false);
+}
+
 @* Scripting QMainWindow.
 
 \noindent Rather than directly exposing |QMainWindow| to the scripting engine,