A power failure and an eternity [my internet speed after a certain usage drops down to blazing-amazing 30KBPS] later I finally gave a spin to 32 bit flavor of VSIDO 2014_01_13.iso. And my impression?
Kudos to VastOne 8)
A job well done 8)
A near perfect experience 8)
9 out of 10 8)
Why only 9 I hear you say ;)
Well only little gripe I had was tint2 housing wicd in the top right corner was clashing with window controls. Close button of any maximize window was inaccessible as clicking there would open wicd menu. This was in live session. Sadly I don't presently have a spare partition so I wasn't able to install this VSIDO image.
VSIDO is for sure going in the right direction.
Cheers.
Thanks for that review hakerdefo
I am aware if the upper right tint2 issue and am working on resolving it... I have tried making fluxbox remember all positions but for some reason not all of them remember correctly for me (xfce4-terminal is one)
I will look for other ways to correct it
I did correct the tint2 issue on the top right... from now on it will always be under any application
Changing it in tint2 breaks the systray function in that panel... Still searching
Thanks!
What are you trying to accomplish (I forget what the default behavior is suppose to be)?
but the combination -
panel_layer = bottom
panel_strut_policy = follow_size
in the tint2rc I used for a pager with a system tray, will reserve space for the tint2 bar and doesn't effect the system tray on my set up.
^ That is why I asked you! 8) ;D
Thanks ... that setting is exactly what was needed, I appreciate it
No problem -
seems to always come down to getting the layer and strut policies matched up correctly. I always have to keep in mind that fluxbox is coded to use 13 layers (not 3) and designed to work with it's native toolbar (panel).
sidebar note - I'm actually delving into that a bit as it relates to iconify and "show desktop".
[end] sidebar #don't derail thread.
^ Do you ever see these settings fail?
I have it running all day on this machine... no issues, but now I cannot do anything with the icons on systray
On the build machines... the settings do not work unless run from terminal or xfrun4... they do not work when ran from FluxBox startup
On a ISO livecd boot, they work from anywhere... but on the install it is back to not working unless run from terminal or xfrun4...
Very strange behavior
Installed the latest 32 bit build and I must say I am impressed as always. This baby burns.
My only gripe will echo hackerdefo regarding the tint2/wicd in that upper right corner.
Have to admit, I find myself booting more and more into VISIDO lately and less into Slackware 8)
^ that is one hell of a compliment zbreaker!
Thanks man!
No I don't see those settings fail, but then again, I don't run that tint2 pager too often - it's basically something to hack on. I use the native fluxbox toolbar, systemtray, and clock for my PackRat account. I have a test usrname (scarecrow) that use for problem solving.
I may have another fix for that tint2 bar with the system tray; do you know if tint2 can be opened with a unique class name. Conky has
own_window_class
own_window_title
does tint2 have an equivalent?
^ No... nothing similar to that at all.. It does have a background id and I tested it but it did not change anything
One of the strangest things I have ever seen..
I am changing it back to what it was as
panel_layer = top
This way I know it works and all a user has to do is move a window / app that may have moved behind that panel
I created a new user so I could get the default aesthetics - took me about 5 min to realize I have the lxpanel version ... doh!
Anyway, set up tint2 panels - one at the bottom, and one with systray and clock up top. I did lose the use of the icons in the systemtray, but got the functionality back when I killed and restarted tint2. Tweaked the sleep settings in the fluxbox startup and have not recreated the issue yet.
Right now I'm leaning toward a startup or start order issue between two tint2 panels, compton, conky when those settings are used.
I was suspecting the same thing... I will test several different variants and orders of the startup until I am comfortable with it
Jedi has told me on the IRC he never sees this behavior and he has extended the sleep time on several tint2 configs that he uses
We shall get to the bottom of it
Thanks Rat Man!
I added a 10s delay to the systray tint2 and it seems to have resolved the issue
Can make that an easy change...
Thanks for the feedback Rat Man!
Beauty lies in the eyes of beholder and personally I prefer only single panel at bottom. Like the one here,
http://vsido.org/index.php?topic=58.msg365#msg365 (http://vsido.org/index.php?topic=58.msg365#msg365)
I've no idea why this one is not default in VSIDO :o
But again "Beauty lies in the eyes of beholder." ;)
Cheers.
Quote from: VastOne on January 20, 2014, 04:30:08 AM
I added a 10s delay to the systray tint2 and it seems to have resolved the issue
Can make that an easy change...
Thanks for the feedback Rat Man!
Here is mine. Works perfect without delay, and I use panel_layer = normal and strut_policy = follow_size.
(I have enabled FBS, and use a different background definition that merges it with the conky, so it all looks like one bar)
Sorry for not using the code-snippet, but for some reason that made the text huuuge...
#---------------------------------------------
# TINT2 CONFIG FILE
#---------------------------------------------
#---------------------------------------------
# BACKGROUND AND BORDER
#---------------------------------------------
# Background definitions
# ID 1
rounded = 0
border_width = 0
background_color = #000000 100
border_color = #000000 0
#---------------------------------------------
# PANEL
#---------------------------------------------
# wm_menu = 1
panel_items = FBS
panel_monitor = all
panel_position = top right
panel_size = 155 35
panel_margin = 0 0
panel_padding = 0 0
font_shadow = 0
panel_background_id = 1
panel_layer = normal
#---------------------------------------------
# SYSTRAYBAR
#---------------------------------------------
systray = 1
systray_padding = 8 2 3
systray_sort = ascending
systray_background_id = 1
systray_icon_size = 35
# Launchers
launcher_icon_theme = LinuxLex-8
launcher_padding = 2 2 2
launcher_background_id = 1
#---------------------------------------------
# CLOCK
#---------------------------------------------
#time1_format = %H:%M
#time1_font = sans 8
#time2_format = %A %d %B
#time2_font = sans 6
#clock_font_color = #ffffff 76
#clock_padding = 4 4
#clock_background_id = 1
#---------------------------------------------
# BATTERY
#---------------------------------------------
battery = 1
battery_low_status = 7
battery_low_cmd = notify-send "battery low"
bat1_font = sans 8
bat2_font = sans 6
battery_font_color = #ffffff 76
battery_padding = 1 0
battery_background_id = 1
#---------------------------------------------
# MOUSE ACTION ON TASK
#---------------------------------------------
mouse_middle = none
mouse_right = none
mouse_scroll_up = toggle
mouse_scroll_down = iconify
# Panel Autohide
autohide = 0
autohide_show_timeout = 0.0
autohide_hide_timeout = 0.0
autohide_height = 3
strut_policy = follow_size
Quote from: VastOne on January 20, 2014, 04:21:15 AM
I was suspecting the same thing... I will test several different variants and orders of the startup until I am comfortable with it
Jedi has told me on the IRC he never sees this behavior and he has extended the sleep time on several tint2 configs that he uses
We shall get to the bottom of it
Thanks Rat Man!
I had it lock up once this morning; a restart of tint2 and all functioning now. Rearranged the startup order, and some other edits to ~/.fluxbox/startup and going well. I suppose the next step is to leave the computer idle for a while and see if the problem returns.
One other thing I tried, in the ~/.fluxbox/init file I now have -
session.screen0.toolbar.tools: prevworkspace, workspacename, nextworkspace,so that there is nothing on that line competing with tint2 - probably overkill.
@ew - what is "F" in the panel_items? Not in the tint2 wiki; I don't follow the progress of tint2 so I am unaware of undocumented items.
I also did a little research this morning and could find no correlation with the 'F' listed in ew's config. If this is a new feature I'd be interested in knowing it's function! Thanks ew, and PackRat your Fluxbox knowledge as well as your vast knowledge on the other WM's you so terrifically represent here is much appreciated!
I had already eliminated the F as the culprit...
@PackRat, the F is from patches supplied from the tint2 sources here (http://code.google.com/p/tint2/issues/detail?id=382&sort=-id%20-type).. for the life of me I cannot figure out why development has stopped on tint2 and nothing more added... I repackaged tint2 to include these patches... if you want the built code let me know
I appreciate the continued help and investigation on this
@hakerdefo ... I like that setup as well and it is included on the ISO, but I thought it would be overkill of a good thing!
Ah, a patch. I suspect that, like the dev for pypanel, the devs for tint2 decided it did what it needed to do and moved on.
No more issues with systray icons not working on my end.
Quote from: VastOne on January 20, 2014, 03:16:20 PM
I had already eliminated the F as the culprit...
@PackRat, the F is from patches supplied from the tint2 sources here (http://code.google.com/p/tint2/issues/detail?id=382&sort=-id%20-type).. for the life of me I cannot figure out why development has stopped on tint2 and nothing more added... I repackaged tint2 to include these patches... if you want the built code let me know
Yes, and the lack of development in tint2 makes me feel that we probably should use another solution. But I love tint2, so it`s hard to actually take the step and leave it for something else. I especially like the possibility to split the taskbar between different virtual desktops. To my knowledge this isn`t possible to duplicate with anything else. All other solutions only shows the taskbar for the active desktop... If I`m wrong, I would be very happy to be corrected :)
I am pretty sure you can get lxpanel to behave on multiple desktops... I never tried it as I am a one desktop kind of person
I still think lxpanel is better, especially for the beginner... when you can right click and make changes, it is easier than learning tint2
Quote from: VastOne on January 21, 2014, 12:21:38 AM
I am pretty sure you can get lxpanel to behave on multiple desktops... I never tried it as I am a one desktop kind of person
I still think lxpanel is better, especially for the beginner... when you can right click and make changes, it is easier than learning tint2
No doubt about it. lxpanel is easier to learn. I have no problems getting lxpanel to behave on multiple desktops, but it does it a little bit different.
Quote from: VastOne on January 20, 2014, 03:16:20 PM
@hakerdefo ... I like that setup as well and it is included on the ISO, but I thought it would be overkill of a good thing!
I think you misunderstood. I wasn't referring to "Right wing of the Gnome3/Shell" version. I was talking about "the single panel/launcher/task manager/systray" here,
(http://www.zimagez.com/miniature/screenshot-10022012-065018pm.php) (http://www.zimagez.com/zimage/screenshot-10022012-065018pm.php)
Cheers.
^ Right... So was I!
???
Quote from: VastOne on January 20, 2014, 04:30:08 AM
I added a 10s delay to the systray tint2 and it seems to have resolved the issue
Can make that an easy change...
Thanks for the feedback Rat Man!
As with all things linux, there are multiple methods to the madness. I solved it by starting compton after fluxbox in the ~/.fluxbox/startup file.
<snip>
# tint2 and conky start before fluxbox - usually about 3s delay for each on my systems
tint2-panel &
tint2-systray
conky
exec fluxbox &
fbpid=$!
# start compositing after everything is loaded up
sleep 1
{
compton
} &
wait $fbpid