18 Jan
2012
18 Jan
'12
8:26 p.m.
Darrell
Re: For example, after configuring Kate with the --use parameter
Exactly where and how (any quotes, etc) did you set the --use
parameter for Kate.
Tell me that and I will experiment and see if I have the same problem.
Keith
18 Jan
18 Jan
8:43 p.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
Re: For example, after configuring Kate with the
--use
parameter
Exactly where and how (any quotes, etc) did you set the
--use
parameter for Kate.
Tell me that and I will experiment and see if I have the
same problem.
Let's see whether I can describe the scenario correctly. :)
I have a kate shortcut button in my quick launch menu. The parameters:
kate --use %u
I don't like editing *.desktop files in $PREFIX (/usr, /opt/trinity, etc.) because a
subsequent package update will overwrite those files and my modifications. Therefore long
ago I got into the habit of using $KDEDIRS, which for me is located in my /usr/local
partition. In my $KDEDIRS kate.desktop:
Exec=kate --use %U
Okay, now that I pasted that, I see my quick launch button uses a lower case %u and my
$KDEDIRS kate.desktop uses an upper case %U. Hmm. Does that make any difference? I
don't know --- I'll look into that.
Back to the discussion.
I have my Focus stealing prevention level set to Low (KControl, Desktop, Window Behavior,
Advanced tab.)
Open kate any which way. Open a text file.
Then in Konqueror, find another text file and open the file in kate.
Does kate pop forward? Does kate have the focus?
When I temporarily change my Focus stealing prevention level to None, which raises havoc
with other desktop usage, then kate will pop forward but will not have the focus.
Just to be sure we are using terms the same, focus means the title bar is highlighted with
the user's selected color and not grayed.
Let me know how things behave on your system. I'll be happy to hear you have none of
those problems. That would mean something awry with my configuration.
Darrell
9:44 p.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
On Wed, Jan 18, 2012 at 3:43 PM, Darrell Anderson
<humanreadable(a)yahoo.com> wrote:
Could you define: Quick Launch Menu in more detail. I searched google
for "Quick Launch Menu" and kde3 and got nothing. I have heard the
term but have no idea what it really is. It sounds like some kind of
drop down menu with a selection list. How would I get one?
Is it part of the KSmoothDock app?
I my case I just put icons up on the toolbar panel and click on them there.
Keith
Re: For
example, after configuring Kate with the --use
parameter
Exactly where and how (any quotes, etc) did you set the
--use
parameter for Kate.
Tell me that and I will experiment and see if I have the
same problem.
Let's see whether I can describe the scenario correctly. :)
I have a kate shortcut button in my quick launch menu. The parameters:
kate --use %u
I don't like editing *.desktop files in $PREFIX (/usr, /opt/trinity, etc.) because a
subsequent package update will overwrite those files and my modifications. Therefore long
ago I got into the habit of using $KDEDIRS, which for me is located in my /usr/local
partition. In my $KDEDIRS kate.desktop:
Exec=kate --use %U
Okay, now that I pasted that, I see my quick launch button uses a lower case %u and my
$KDEDIRS kate.desktop uses an upper case %U. Hmm. Does that make any difference? I
don't know --- I'll look into that.
Back to the discussion.
I have my Focus stealing prevention level set to Low (KControl, Desktop, Window Behavior,
Advanced tab.)
Open kate any which way. Open a text file.
Then in Konqueror, find another text file and open the file in kate.
Does kate pop forward? Does kate have the focus?
When I temporarily change my Focus stealing prevention level to None, which raises havoc
with other desktop usage, then kate will pop forward but will not have the focus.
Just to be sure we are using terms the same, focus means the title bar is highlighted
with the user's selected color and not grayed.
Let me know how things behave on your system. I'll be happy to hear you have none of
those problems. That would mean something awry with my configuration.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
10:22 p.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
Could you define: Quick Launch Menu in more detail.
I
searched google
for "Quick Launch Menu" and kde3 and got nothing. I
have heard the
term but have no idea what it really is. It sounds
like some kind of
drop down menu with a selection list. How would I get
one?
Is it part of the KSmoothDock app?
I my case I just put icons up on the toolbar panel and
click on them there.
Well, I suppose on reflection there is no such thing in TDE. :) I place a few panel
buttons on the far left side, adjacent to the T-Menu button. My Task bar is to the right
of those buttons. In some systems that area is called a quick launch bar.
So just add buttons to your panel and you'll have the same effect. But you can start
kate using krunner using kate --use. The real point of the bug report is that once kate is
open, double-clicking on text files from within konqueror does not bring kate forward and
kate does not grab the focus.
Darrell
10:32 p.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
On Wed, Jan 18, 2012 at 5:22 PM, Darrell Anderson
<humanreadable(a)yahoo.com> wrote:
OK I will test it tonight after dinner...
I assume buttons = icons. Isn't English a wonderful way to miscommunicate?
I have not used krunner (at least deliberately), I have used kstart,
if you haven't you might want to check it out...
I just checked and (at least in my packaging system), krunner is a
KDE4 app. I don't have any of that on my system so I can't test it
But using a KDE4 app to start a Trinity binary might not give the
expected result...
Keith
Could you
define: Quick Launch Menu in more detail. I
searched google
for "Quick Launch Menu" and kde3 and got nothing. I
have heard the
term but have no idea what it really is. It sounds
like some kind of
drop down menu with a selection list. How would I get
one?
Is it part of the KSmoothDock app?
I my case I just put icons up on the toolbar panel and
click on them there.
Well, I suppose on reflection there is no such thing in TDE. :) I place a few panel
buttons on the far left side, adjacent to the T-Menu button. My Task bar is to the right
of those buttons. In some systems that area is called a quick launch bar.
So just add buttons to your panel and you'll have the same effect. But you can start
kate using krunner using kate --use. The real point of the bug report is that once kate is
open, double-clicking on text files from within konqueror does not bring kate forward and
kate does not grab the focus.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
10:50 p.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
I assume buttons = icons. Isn't English a
wonderful
way to miscommunicate?
Yup. I have worked as a technical writer for more than two decades. Saying what you mean
is always a challenge. :)
I have not used krunner (at least deliberately), I
have
used kstart,
if you haven't you might want to check it out...
I just checked and (at least in my packaging system),
krunner is a
KDE4 app. I don't have any of that on my system so I
can't test it
But using a KDE4 app to start a Trinity binary might not
give the
expected result...
My fault. I always call the Alt-F2 widget "krunner." I suppose in the pre KDE4
days that is technically incorrect. I think in KDE3/TDE the wonderful name is "Run
Command." :)
Darrell
11:45 p.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
On Wed, Jan 18, 2012 at 5:50 PM, Darrell Anderson
<humanreadable(a)yahoo.com> wrote:
When I set the icon in the panel to --use nothing happened in
Konqueror. I got the same response as I did before, i.e. it opened a
new window.
I checked:
/home/keith/.kde3/share/apps/kicker/kate.desktop
and
/home/keith/.local/share/applications/kde-kate.desktop
kate.desktop had the --use option added but apparently Konqueror was
not using that to open Kate.
I checked kde-kate.desktop file and --use had not been added to it.
Since I had no clue what program would set --use in it, I set it by
hand.
After I did that, when I started a text file in Konqueror it reacted
as you described in your bug report.
I did a lot of testing of different CLI options in the
kde-kate.desktop file and most but not quite all would not work when
--use was used.
I tried Kstart in the kde-kate.desktop file and tested it with various
Kstart and Kate options and got the same results as above, most of the
options were ignored.
I tried starting Kate from a terminal, with various options, and had
similar responses as the above--many options quit working when -use
was used.
Keith
I assume
buttons = icons. Isn't English a wonderful
way to miscommunicate?
Yup. I have worked as a technical writer for more than two decades. Saying what you mean
is always a challenge. :)
I have not used krunner (at least deliberately),
I have
used kstart,
if you haven't you might want to check it out...
I just checked and (at least in my packaging system),
krunner is a
KDE4 app. I don't have any of that on my system so I
can't test it
But using a KDE4 app to start a Trinity binary might not
give the
expected result...
My fault. I always call the Alt-F2 widget "krunner." I suppose in the pre KDE4
days that is technically incorrect. I think in KDE3/TDE the wonderful name is "Run
Command." :)
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
19 Jan
19 Jan
12:02 a.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
After I did that, when I started a text file in
Konqueror
it reacted
as you described in your bug report.
I did a lot of testing of different CLI options in the
kde-kate.desktop file and most but not quite all would not
work when
--use was used.
I tried Kstart in the kde-kate.desktop file and tested it
with various
Kstart and Kate options and got the same results as above,
most of the
options were ignored.
I tried starting Kate from a terminal, with various
options, and had
similar responses as the above--many options quit working
when -use
was used.
Well now. How about that?
Would you add some comments in the bug report that you confirmed the behavior? Mention
your operating system too so we know this is not distro related.
By the way, in the Advanced, Special Window Settings, there is a tab named Workarounds. I
have had no luck trying to use those options to fine tune kate's behavior.
Darrell
2:17 a.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
Will do...
I have nothing in my control pannel called "Special Windows Settings"
I do have Desktop >> Window Behavior >> Advanced.
Is that what you are talking about?
If so I keep everything there hid, unchecked or disabled. I don't
like animated inanimate objects, things that jump around when my mouse
passes over them or hyper active desktop borders.
I do have Focus stealing set on low though...
Keith
On Wed, Jan 18, 2012 at 7:02 PM, Darrell Anderson
<humanreadable(a)yahoo.com> wrote:
After I did
that, when I started a text file in Konqueror
it reacted
as you described in your bug report.
I did a lot of testing of different CLI options in the
kde-kate.desktop file and most but not quite all would not
work when
--use was used.
I tried Kstart in the kde-kate.desktop file and tested it
with various
Kstart and Kate options and got the same results as above,
most of the
options were ignored.
I tried starting Kate from a terminal, with various
options, and had
similar responses as the above--many options quit working
when -use
was used.
Well now. How about that?
Would you add some comments in the bug report that you confirmed the behavior? Mention
your operating system too so we know this is not distro related.
By the way, in the Advanced, Special Window Settings, there is a tab named Workarounds. I
have had no luck trying to use those options to fine tune kate's behavior.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
3:36 a.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
I have nothing in my control pannel called
"Special Windows
Settings"
I do have Desktop >> Window Behavior >>
Advanced.
Is that what you are talking about?
Pretty much. Right-click on kate's title bar, select Advance, Special Window Settings.
Same as KControl, just limited to kate.
Darrell
3:48 a.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
Le mercredi 18 janvier 2012, Darrell Anderson a écrit :
Window
Settings. Same as KControl, just limited to kate.
I have nothing
in my control pannel called "Special Windows
Settings"
I do have Desktop >> Window Behavior >>
Advanced.
Is that what you are talking about?
Pretty much. Right-click on kate's title bar, select Advance, Special
Darrell
---------------------------------------------------------------------
+1 ;-)
Lovely. I did not know this tip. I'll probably never use but I like a lot!
Patrick
3:22 p.m.
New subject: [trinity-devel] Bug 692 - Kate: focus is broken when using the --use parameter
On Wed, Jan 18, 2012 at 10:48 PM, Patrick Serru <patrick(a)serru.net> wrote:
Le mercredi 18 janvier 2012, Darrell Anderson a écrit
:
Window
Settings. Same as KControl, just limited to kate.
If you try the Fullscreen choice it is very hard to get a regular
sized window with frames back in Opera and some other programs. Kate
has a menu choice to do that but Opera's did not work.
Keith
I have
nothing in my control pannel called "Special Windows
Settings"
I do have Desktop >> Window Behavior >>
Advanced.
Is that what you are talking about?
Pretty much. Right-click on kate's title bar, select Advance, Special
Darrell
---------------------------------------------------------------------
+1 ;-)
Lovely. I did not know this tip. I'll probably never use but I like a lot!
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
4490
days inactive
4491
days old
11 comments
3 participants
participants (3)
-
Darrell Anderson -
Keith Daniels -
Patrick Serru