--Boundary-00=_IUCzBY1Lj8uew2s Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi all, I found the following question on the kde list, and reading the answer, I a= sk=20 myself if it is understandable by a newbie to find the "Link to Location ..= =2E"=20 below the "File" menu. (Also, as I do not create a Device itself, it should be called "Link to=20 device") I propose to move the entries "Link to Application" and "Link to Location" = one=20 level up, so that I have create new-> * Folder ... * Link To Application ... * Link to Location ... * File >> =20 * Link To Device >> Do you think the attached patch is OK ? =2D--------- Forwarded Message ---------- Subject: Re: [kde] creating a link to a directory Date: Monday 20 December 2004 11:42 =46rom: icebox To: kde@mail.kde.org, jsowden@americansentry.net On Monday 20 December 2004 08:32, John Sowden wrote about [kde] creating a link to a directory: > I am trying to create a link to a directory where I have some > programs to run. I don't want to start the browser (url), just open a > window to a directory, but not the desktop. How do I associat an > icon on the desktop to, say,: /home/john/accounting > > thanks, > >(...) Right click on the desktop, Go to: Create New -> File -> Link to location. =2D-=20 Best regards/Sch=F6ne Gr=FC=DFe Martin () ascii ribbon campaign - against html mail=20 /\ - against microsoft attachments Some operating systems are called 'user friendly', Linux however is 'expert friendly'. --Boundary-00=_IUCzBY1Lj8uew2s Content-Type: text/x-diff; charset="iso-8859-1"; name="newmenu.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="newmenu.patch" Index: knewmenu.cc =================================================================== RCS file: /home/kde/kdebase/libkonq/knewmenu.cc,v retrieving revision 1.99 diff -u -3 -p -r1.99 knewmenu.cc --- knewmenu.cc 6 Nov 2004 17:04:51 -0000 1.99 +++ knewmenu.cc 24 Dec 2004 14:14:26 -0000 @@ -93,7 +93,7 @@ KNewMenu::~KNewMenu() void KNewMenu::makeMenus() { - d->m_menuDev = new KActionMenu( i18n( "Device" ), "kcmdevices", d->m_actionCollection, "devnew" ); + d->m_menuDev = new KActionMenu( i18n( "Link to Device" ), "kcmdevices", d->m_actionCollection, "devnew" ); d->m_menuNew = new KActionMenu( i18n( "File" ), "filenew", d->m_actionCollection, "devnew" ); } @@ -235,8 +235,10 @@ void KNewMenu::fillMenu() { Entry entry = *(s_templatesList->at( i-1 )); - // The best way to identify the "Create Directory" was the template - if((*templ).templatePath.right( 8 ) == "emptydir") + // The best way to identify the "Create Directory", "Link to Location", "Link to Application" was the template + if ( ((*templ).templatePath.endsWith( "emptydir" )) || + ((*templ).templatePath.endsWith( "URL.desktop" )) || + ((*templ).templatePath.endsWith( "Program.desktop" )) ) { KAction * act = new KAction( (*templ).text, (*templ).icon, 0, this, SLOT( slotNewDir() ), d->m_actionCollection, QCString().sprintf("newmenu%d", i ) ); @@ -319,7 +321,9 @@ void KNewMenu::slotFillTemplates() e.filePath = *it; e.entryType = 0; // not parsed yet // put Directory first in the list (a bit hacky) - if ( (*it).endsWith( "Directory.desktop" ) ) + if ( (*it).endsWith( "Directory.desktop" ) || + (*it).endsWith( "linkProgram.desktop" ) || + (*it).endsWith( "linkURL.desktop" ) ) s_templatesList->prepend( e ); else { --Boundary-00=_IUCzBY1Lj8uew2s Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kde-usability mailing list kde-usability@kde.org https://mail.kde.org/mailman/listinfo/kde-usability --Boundary-00=_IUCzBY1Lj8uew2s--