settings

I have been looking at the sample app provided by InAppSettingsKit and I noticed the use of a couple of buttons: I would like to integrate a single red button in my app called reset, however I'm not sure how to do it. I've had a look at the code in the sample app and I'm a bit lost with it all. Please could someone help me out? After spending a while searching through all the code and plists I managed to find the answer to my question. For those who are interested what you need to do is the following: Add a row to your Root.plist file with the Type set to IASKButtonSpecifier . Set the

In Apigility it's possible to set a Hydrator for every Entity -- either over the Apigility UI or directly in the module.config.php , e.g.: return array( ... 'zf-hal' => array( 'metadata_map' => array( 'Portfolio\\V2\\Rest\\Project\\ProjectEntity' => array( 'entity_identifier_name' => 'id', 'route_name' => 'portfolio.rest.project', 'route_identifier_name' => 'id', 'hydrator' => 'Zend\\Stdlib\\Hydrator\\ObjectProperty', // 'hydrator' => 'MyNamespace\\Hydrator\\ProjectHydrator', ), ... ), ... ), ... ); See also the documentation . Currently I'm using the ClassMethods hydrator for all my entities.

I have tried the great Google example to sync contact from a webservice and that work fine. This is called the SampleSyncAdapter and really worth it: http://developer.android.com/resources/samples/SampleSyncAdapter/index.html I succed everything, but I cannot found in the example nor in the documentation a way to add a category that would link to a custom activity, exactly like the screenshot below: (I have only the sync account option with the checkbox) So, my question is: how can I add the account settings category? ehartwell herschel 's answer provides a link to a generic solution. Here's

I just discovered join_collapse_limit has been preventing the PostgreSQL planner from finding a much better join order. In my case, increasing the limit to 10 (from the default of 8) allowed the planner to improve search time from ~30 secs to ~1 ms, which is much more acceptable. The documentation suggests that setting this "too high" could result in long planning times, but does not provide even a "rule of thumb" about how long the planning step might be for various values. I understand the general problem is exponential in time, but I cannot find a way to determine the actual planning time

In .NET you can select a hashtable as type for a usersetting. However when I save it and retrieve it in this way, it doesnt seem to have saved it at all. Hashtable t = new Hashtable(); t.Add(1,"Foo"); t.Add(2,"Bar"); Properties.Settings.Default.Setting = t; Properties.Settings.Default.Save(); if(Properties.Settings.Default.Setting != null) foreach (DictionaryEntry entry in Properties.Settings.Default.Setting) { MessageBox.Show(entry.Key + " " + entry.Value); } Why doesnt it serialize it in the usersettings, when I can clearly select that type in Visual studio? I would understand if this was