Development/FAQs/Technical FAQ - Revision history

AnneW: Marked this version for translation

2012-07-13T12:41:50Z

Marked this version for translation

AnneW at 12:41, 13 July 2012

2012-07-13T12:41:30Z

AnneW: Marked this version for translation

2012-01-23T17:22:47Z

Marked this version for translation

Show changes

AnneW at 17:22, 23 January 2012

2012-01-23T17:22:39Z

Show changes

Phanect: Added tags.

2012-01-22T21:26:53Z

Added <translate> tags.

Neverendingo: Text replace - "" to ""

2011-06-29T19:15:58Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T19:13:35Z
Text replace - "<code cppqt>" to "<syntaxhighlight lang="cpp-qt">"

				
				
				
				
			
			← Older revision
			Revision as of 19:13, 29 June 2011
			
Line 181:
Line 181:
    
  Never make assumptions about the geometry of the "desktop" or the arrangement of the screens. Make use of the following functions from kglobalsettings.h:     Never make assumptions about the geometry of the "desktop" or the arrangement of the screens. Make use of the following functions from kglobalsettings.h:  
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
    static QRect KGlobalSettings::splashScreenDesktopGeometry();       static QRect KGlobalSettings::splashScreenDesktopGeometry();  
    static QRect KGlobalSettings::desktopGeometry(const QPoint& point);       static QRect KGlobalSettings::desktopGeometry(const QPoint& point);



Alisha at 06:33, 5 December 2009
2009-12-05T06:33:31Z

Show changes


Alisha at 02:00, 5 December 2009
2009-12-05T02:00:49Z


				
				
				
				
			
			← Older revision
			Revision as of 02:00, 5 December 2009
			
Line 108:
Line 108:
  ====I get "virtual tables error"?====   ====I get "virtual tables error"?====
  This often comes from the moc files not being in sync with the sources, or not linked at all. Check that you are running the right moc. 'which moc' will tell it. Regenerate your moc files (make force-reedit; make clean; make).     This often comes from the moc files not being in sync with the sources, or not linked at all. Check that you are running the right moc. 'which moc' will tell it. Regenerate your moc files (make force-reedit; make clean; make).  
−  
− ====Trying to use dcop, I just added k_dcop to myClassHeader.h file but nothing specific seems to happen?====  
− Add myClassHeader.kidl to your Makefile.am and run make again.  
−  
− ====Some Makefile.am have a .stub file, what is it for?====  
−  
− Stubs are not very documented. A stub allow you to view a dcop registered application as an object whose methods are its dcop slots. Usually, applications have an appnameIface.h file that contains all the dcop slots. Add a appnameIface.stub in your Makefile.am and use the object appnameIface. See for example kdebase/khelpcenter that uses a konqueror stub.  
    
  ====I have added Q_OBJECT to myClassHeader.h but no moc files is generated?====   ====I have added Q_OBJECT to myClassHeader.h but no moc files is generated?====



Alisha at 16:45, 4 December 2009
2009-12-04T16:45:46Z


				
				
				
				
			
			← Older revision
			Revision as of 16:45, 4 December 2009
			
Line 1:
Line 1:
  {{Template:I18n/Language Navigation Bar|Development/FAQs/Technical FAQ}}   {{Template:I18n/Language Navigation Bar|Development/FAQs/Technical FAQ}}
  + {{improve|The build system has changed in KDE4.}}
  ====How do I start a new application?====   ====How do I start a new application?====
− {{improve|The build system has changed in KDE4. This section is obsolete.}}  
    
− The easiest way is to use kdesdk/kapptemplate or kdevelop to generate the Makefile.am . Or you can just copy a Makefile.am from another app and install it in a new toplevel directory of existing KDE sources. Or you can start the old way, from scratch, but you'll miss the power of the autoconf/automake framework.   + The easiest way is to use kdesdk/kapptemplate to generate the CMakeLists.txt. Or you can just copy a CMakeLists.txt from another app and install it in a new toplevel directory of existing KDE sources. Or you can start the old way, from scratch.  
    
  ====What is plasma, kpart, kio, kdeinit, ...====   ====What is plasma, kpart, kio, kdeinit, ...====

@@ Line 185: / Line 185: @@
   static QRect KGlobalSettings::desktopGeometry(const QPoint& point);
   static QRect KGlobalSettings::desktopGeometry(QWidget *w);
-</code>
+</syntaxhighlight>
 Use splashScreenDesktopGeometry() to determine the geometry of the desktop when you want to display an application splash screen. Use desktopGeometry() to determine the geometry of the desktop with respect to a given point on the desktop, or with respect to a given widget. Do not use the Qt class QDesktopWidget to determine these values yourself. The KDE functions take the user's settings into account, something the Qt functions cannot do.

@@ Line 1: / Line 1: @@
 <languages />
 <translate>
 {{improve|The build system has changed in KDE4.}}