Sounds in my ears like you should refactor your application, and extract the functionality that generates the string out to a new seperate class (or reuse an existing class, if you have one that fits) and let both controllers use that class.
You can silence the Rails logger object: def action Rails.logger.silence do # Things within this block will not be logged… end end
Try using Response.SetCookie(), because Response.Cookies.Add() can cause multiple cookies to be added, whereas SetCookie will update an existing cookie.
Give each input a name attribute. Only the clicked input‘s name attribute will be sent to the server. <input type=”submit” name=”publish” value=”Publish”> <input type=”submit” name=”save” value=”Save”> And then <?php if (isset($_POST[‘publish’])) { # Publish-button was clicked } elseif (isset($_POST[‘save’])) { # Save-button was clicked } ?> Edit: Changed value attributes to alt. Not sure this … Read more
You should stop the submit procedure by returning false on the onsubmit callback. <script> function checkRegistration(){ if(!form_valid){ alert(‘Given data is not correct’); return false; } return true; } </script> <form onsubmit=”return checkRegistration()”… Here you have a fully working example. The form will submit only when you write google into input, otherwise it will return an … Read more
How about this workaround? private Action<string, object[]> writeToLogCallBack; public void WriteToLogCallBack(string s, params object[] args) { if(writeToLogCallBack!=null) writeToLogCallBack(s,args); } Or you could define your own delegate type: delegate void LogAction(string s, params object[] args);
Edit. Found a neater way! One argument that the button can receive is (id)sender. This means you can create a new button, inheriting from UIButton, that allows you to store the other intended arguments. Hopefully these two snippets illustrate what to do. myOwnbutton.argOne = someValue [myOwnbutton addTarget:self action:@selector(buttonTouchUpInside:) forControlEvents:UIControlEventTouchUpInside]; and – (IBAction) buttonTouchUpInside:(id)sender { MyOwnButton … Read more
It’s been some time since I posted the question, which was quite colored by my little experience and knowledge of MVC. Still I received some quite useful input, that eventually led me to find a solution and also gain some insight of MVC. What threw me off in the first place, was that you could … Read more
Click on the green plus sign after you selected the signals Slots Editor. It will give you 4 fields to fill in. For sender you select what is creating the signal. For example ActionExit might be the name you created for the exit menu item. The signal is probably going to be clicked(). The receiver … Read more
This is not specific to JSF. This is specific to HTML. The HTML5 forms specification section 4.10.22.2 basically specifies that the first occuring <input type=”submit”> element in the “tree order” in same <form> as the current input element in the HTML DOM tree will be invoked on enter press. There are basically two workarounds: Use … Read more