On Friday I pushed all the UX related source repositories to gitorious @ https://meego.gitorious.org/meego-ux, with the plan of taking advantage of the merge request mechanism for reviewing/accepting incoming patches.

Please convert this (and the other related patches) to merge request and give me a chance to try out the merge request mechanism.

    --rusty

On 03/26/2011 02:26 PM, Robin Burchell wrote:
Signed-off-by: Robin Burchell<[email protected]>
---
  application.cpp |    6 +++---
  1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/application.cpp b/application.cpp
index 1de036e..878c08a 100644
--- a/application.cpp
+++ b/application.cpp
@@ -90,7 +90,7 @@ Application::Application(int&  argc, char ** argv, bool 
opengl) :
      m_homeActive(false),
      m_homePressTime(0),
      
m_haveAppStore(QFile::exists("/usr/share/applications/com.intel.appup-tablet.desktop")),
-    m_foregroundOrientation(2),
+    m_foregroundOrientation(1),
      m_notificationDataStore(NotificationDataStore::instance()),
      m_notificationModel(new NotificationModel),
      m_lastNotificationId(0)
@@ -148,7 +148,7 @@ Application::Application(int&  argc, char ** argv, bool 
opengl) :
      MGConfItem *landscapeItem = new 
MGConfItem("/meego/ux/PreferredLandscapeOrientation", this);
      if (!landscapeItem || landscapeItem->value() == QVariant::Invalid)
      {
-        m_preferredLandscapeOrientation = 1;
+        m_preferredLandscapeOrientation = 0;
      }
      else
      {
@@ -158,7 +158,7 @@ Application::Application(int&  argc, char ** argv, bool 
opengl) :
      MGConfItem *portraitItem = new 
MGConfItem("/meego/ux/PreferredPortraitOrientation", this);
      if (!portraitItem || portraitItem->value() == QVariant::Invalid)
      {
-        m_preferredPortraitOrientation = 2;
+        m_preferredPortraitOrientation = 1;
      }
      else
      {

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to