Apply config button terminates tint2

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Hit the apply config button
2.
3.

What is the expected output? What do you see instead?
A dialogue pops up explaining that tint2 will be terminated.  I would like 
it to 1. shut down tint2, 2. update the tint2 config file, then 3. reload 
tint2 persistently, as it was before (I assume for most people).  If this 
is not the desired result for everyone, on the dialogue that pops up 
explaining that tint2 will be shut down, give the option to have it reload 
permanently after applying the changes.

What version of the product are you using? On what operating system?
0.21, #! 9.04.

Please provide any additional information below.
Nice work, I love this app!

Original issue reported on code.google.com by lewi...@gmail.com on 27 Aug 2009 at 9:48

[GoogleCodeExporter]

Sorry, didn't know that "enhancements" was an option, this is not a bug, I 
should have 
labeled it "enhancement."

Original comment by lewi...@gmail.com on 27 Aug 2009 at 9:49

[GoogleCodeExporter]

Hi there,
I'm not entirely sure that I understand what you are saying. Do you want to be 
able
to revert back to your previous tint2 config if you do not like the changes 
that were
made? Or have I misinterpreted your suggestion. I'd appreciate if you could 
clear
this up for me.

Thanks for taking the time to do this!

Original comment by eua...@gmail.com on 27 Aug 2009 at 10:07

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

The first time I tried it, I loaded my current config file to edit.  I made 
changes, 
and when I hit "apply config" it showed the "this will terminate any running 
tint2 
processes" dialogue.  After closing tintwizard, my tint2 panel disappeared.  I 
assumed that dialogue meant I would then have to restart tint2.

My request was that it would then "reload" tint2 so I had a running panel after 
editing, applying, then exiting the program.

I just made another change using tintwizard, hit apply config, and exited the 
program.  This time my panel remained intact with the new config.  This is the 
expected behaviour, so if thats the way its supposed to work, then when I had 
the 
problem yesterday, it must have been an anomaly.

Original comment by lewi...@gmail.com on 28 Aug 2009 at 4:22

[GoogleCodeExporter]

Thanks, Lewis.

The first problem should not have happened; tint2 should exit, and then reload 
with
the new config. After you exit tintwizard, tint2 SHOULD remain running with 
your new
config.

It's good that everything worked as expected the second time. I'm afraid that I 
have
no idea what caused things to go wrong the first time, but as I continue to 
test the
application on different distros, I might be able to find what is causing 
problems.

Thanks for your time in filing the bug report :)

Original comment by eua...@gmail.com on 28 Aug 2009 at 4:39

[GoogleCodeExporter]

Check out like 1147.
os.spawnv(os.P_NOWAIT, self.tint2Bin, [self.tint2Bin, "-c" + self.filename])
Should read:
os.spawnv(os.P_NOWAIT, self.tint2Bin, [self.tint2Bin, "-c", self.filename])

Why it worked at all is a mystery to me...

Original comment by rectifie...@gmail.com on 21 Apr 2010 at 8:07

[GoogleCodeExporter]

Thanks. What a silly mistake for me to make... Surprised it actually worked for 
so 
long! Fixed.

Original comment by eua...@gmail.com on 21 Apr 2010 at 8:21