By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1127 - Kate: Add the ability to force Kate into MDI mode all the time
Summary: Kate: Add the ability to force Kate into MDI mode all the time
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All Linux
: P5 enhancement
Assignee: Calvin Morrison
URL:
Depends on:
Blocks:
 
Reported: 2012-07-26 13:11 CDT by Darrell
Modified: 2013-08-17 14:47 CDT (History)
5 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Preliminary patch to enforce MDI (5.33 KB, patch)
2012-07-26 13:11 CDT, Darrell 		Details | Diff
Updated patch for latest GIT which also fixes the About dialog (5.57 KB, patch)
2013-05-09 10:04 CDT, Timothy Pearson 		Details | Diff
Show Obsolete (2) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2012-07-26 13:11:49 CDT 
Created attachment 711 [details]
Preliminary patch to enforce MDI

Long ago Kate originally was a Multiple Document Interface (MDI) app. Starting in the KDE 3.5 series, Kate was changed to the Single Document Interface (SDI). With that change a kludge to somewhat support MDI behavior was added through the --use parameter. The --use parameter works only most of the time. Reading bug reports, forum discussions, and blogs indicate that this change from MDI to SDI never has worked completely and has frustrated many users.

During the effort to resolve bug report 692, a preliminary patch was submitted to enforce a true MDI. That patch was not needed to resolve bug report 692 but nonetheless has promise as a new feature. The patch was working okay but had a bug in that the Kate About dialog information disappeared.

The patch also needs further usability testing. For example, users who prefer the SDI should be involved to ensure the patch does not prevent their preferred usage.

The patch is being moved from bug report 692 to this new enhancement request.
Comment 1 Timothy Pearson 2013-05-09 10:04:19 CDT 
Created attachment 1249 [details]
Updated patch for latest GIT which also fixes the About dialog
Comment 2 Timothy Pearson 2013-05-09 10:05:18 CDT 
Please test for desired functionality.  If there are no regressions this patch can be pushed to GIT.
Comment 3 Darrell 2013-05-09 13:35:14 CDT 
Patch applied and rebuilt. This took me a while to test because I have kate configured everywhere with the --use option, even in a bash alias. I had to disable all of that. :-)

First, no problems with an empty About dialog. Looks good.

The patch seems to work as intended, at least within the scope of my thinking. When the new MDI option is enabled, opening files from konqueror or the command line results in kate opening in the same instance. When disabled kate uses a separate instance.

I configured root's kate settings the same way and then tested with tdesu. The same tdesu instance was used. When disabled then each tdesu session opened in a separate instance.

A note:

I am confused about one related area.

The default kate.desktop in the tdebase sources contains the --use option. That would seem to mean kate should always use the currently open instance but that is not what I see. When the new MDI option is disabled, kate opens in separate instances rather than the same instance.

Yet with the new MDI option disabled, when I open a file from konsole using kate --use then the file opens in the current instance of kate.

My thinking is because the installed kate.desktop contains the --use option, when the new MDI option is disabled kate should still open all files in the same instance. So please correct me if I'm misunderstanding the --use option.
Comment 4 Darrell 2013-08-06 16:47:58 CDT 
I've been using this patch for some time. No problems I can see. How about we push to git?
Comment 5 Darrell 2013-08-17 14:47:10 CDT 
Patch pushed to git in commit f3db9433.