a few minor changes (inline comments :)
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
May 19 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 18 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 17 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 16 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 15 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 13 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 12 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 11 2022
a few minor changes (inline comments :)
May 10 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 9 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
I was busy setting up gitea to replace phab and gitolite... phab will eventually die so for now this conversation is working through ideas :) it's not a ticket that will actually really exist long-term. (git.enlightenment.org now is gitea).
May 8 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 7 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 6 2022
a few minor changes (inline comments :)
May 5 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
May 3 2022
a few minor changes (inline comments :)
May 2 2022
there's actually a bug here where too many notifications cause E to crash
May 1 2022
So this might be some of the disconnect here. 100% of my notifications are OSD from the OS. I have no notifications from the browser precisely for the same reasoning, due to how they override the nature of the system.
Apr 30 2022
a few minor changes (inline comments :)
a few minor changes (inline comments :)
a few minor changes (inline comments :)
There are a few classes of applications in particular that do not respect window management. Java applets are some of the worst. If you need a specific example, I can point to a project or two on GitHub.
Apr 28 2022
so question now is - are you planning on doing anything here or are you more trying to convince me to do this and re-dd this back?
Apr 25 2022
desktop files in ~/.local are to be maintained by the user... so - this is an issue that the user is not maintaining them... :) every check you do to verify something badly maintained costs overhead and certainly something like ibar that is explicitly maintained by a user to only have in it what they want to be there is thee uswer's job.
Apr 22 2022
ibar can't have an icon for an app that is not installed... the desktop file must exist for it to appear. your problem is you have a desktop file for something you don't have. the problem you have is that desktop file... it's advertising the existence of something that is not there.
even if listed in the .order file - it will not show if the .desktop file is not found. if the desktop file appears again the icon will appear.
Apr 17 2022
This still doesn't address working with multiple windows or the applications that simply do not play nice with window decorations.
Mar 22 2022
well you can set any window to be full-screen you know... it's in the menu and ctrl+alt+f toggles it... :) so ... i'd like to know how this is not sufficient? you know you can set up keybindings to toggle screen blanking on/off - there are actions for it... :)
disabling notifications is a new thing - though not sure that should have to do with this mode - more like;y disable them if you have a fullscreen window... ? so something in the notification settings.
Feb 24 2022
not going to add xmbed at all. it has far too many gotchas/problems. doesn't port to wayland. doesn't allow multiple instances. totally screws up look of icons (squares). most xmebd apps do not handle xmbed "tray provider" disappearing and re-appearing (ie when e restarts) etc. ... so my guess is these apps don't do indicator protocol like you had they issue with nm-applet and they need to move on or just not work.
Feb 23 2022
8ba3da9bcae03d3c44a6cb066e4e6a64c1540773 committed it
Feb 22 2022
well ask on #e - i believe simotek and others have used nm-applet with this and it has worked. they had to compile with this enabled though.
Feb 21 2022
i can only comment about nm-applet but you have to specifically enable appindicator support at compile time... otherwise it wont' support it. people are using it successfully with this enabled. i assume all the rest above are the same - they do xmbed only.
Feb 1 2022
6ed1e6199687bd55fb93025720d6a345eb6f1af3 fixes this.. i hope
Jan 18 2022
try another icon theme? apps here have icons - gtk or not. your xfce icon there will be for a gtk app too.. so nothing to do with gtk really... more to do with either e just has no icon at all from the icon theme, or the window doesnt expose enough properties to match up to an icon theme (very unlikely).
e_comp_x.c - look for all the callbacks handling x events and then add printfs in each to see what is going on... like _e_comp_x_reparent() _e_comp_x_hide() _e_comp_x_show() and do on - the ones that have some Ecore_X_Event_xxxxx as the last parameter. especially things like _e_comp_x_focus_out(), _e_comp_x_focus_in() and _e_comp_x_client_property() also what happens to focus timers ... there is a lot there and this may require a lot of chasing to find out what is going on.
oooh so something in config...
Jan 17 2022
i guess i should just make the size a scale 0->8 or something with 1.0 being 32 ...
ok - i had to both teach code to emit signals to left/right align when in vertical mode and to handle them in theme too as you want - that's why i ha no solution. needed new code and new theme stuff
you can send a patch when you find it... :) i can't do anything.. i don't see any issues... as i have shown... i cant go fix something when i dont know what it is. but gtk3 is broken in DRAWING the focus state of a CSD frame as i mentioned above. that's a gtk bug.
that's not how themes work - you don't just get to customize every bitmap that e or efl uses. there are 1000's of them. this is what themes do. there is no way to just "choose a bitmap" because a pointer might be made up of many bitmaps and other elements overplayed and some scale, some don't. some animate (the blue rect that changes is an example - its a rect added to the cursor image that animates - the cursor is both of these together in 1 groups/element that defines this layout and behavior). you CAN go make a custom theme to do whatever you like - but i can't sensibly make a ui where everything is selectable in the ui.
oh you change the size... like manually. not relying on scaling.i actually use scale = 1... normally on my desktop. i don't scale i tup. i test scaling on a laptop next to me at scale = 2.... changing cursor size manually actually doesn't even scale the cursor (properly) BECAUSE it now scales with the theme - because theme sets the cursor base image to be 32x32 MULTIPLIED by scale factor... and your manual changing of cursor size actually just reduces the cavas area of a cursosr but doesn't affect scaling. this is a bug allowing setting of the cursor SIZE. this should actually be removed as it's a feature from the very first e17 code years before e17 was released and before we properly did scaling for everything like we do now.
Jan 16 2022
well ... i can't see the problem... i really can't know what's happening - there is just so so so much code and logic that i can't even guess. it shouldn't disappear. I don't see this as an nvidia issue though - if the window disappears then the window really has gone - either e is hiding it or the app is - in this case likely e is hiding it.. but i don't know why - i don't see it happen so i have no idea how it gets into this state. if e thinks the window is there you should at least see the outline of a border/frame and the window content be empty if something is wrong with the client pixmap...
the mouse pointer is the SAME size in flat as previous theme.... the difference is pointer is now tagged to scale to it scales with the rest of the theme. scale = 2 ... would hve it be 2x as bit in pixels. scale = 0.8 will be 0.8 times the size... scale 1 will be the exact same size as previous theme... and actually the old cursor is a bit smaller due to the deep black outline using up pixels. here -i scaled the new 128x128 image to 32x32 and pasted it beside the old one:
unfortunately i don't have a solution - the overlayed label is centered - it doesn't have any signals to tell it orientation - in fact ibar doesnt do this to any icons. my solution is probably just "turn the label off". :) you know what the icons are anyway... :)
I do not think the window disappeared. its just below firefox. try just moving firefox out of the way.
yup... tested. broken for sure in fvwm2, twm and in e - at least in displaying if the window looks focused or not. this would be a gtk3 bug. 100%. not your bug you have exactly but there is an indication that gtk3 is not doing things right.
then you're almost totally up to date. nothing that will affect focus or window stacking etc. ... i cannot see/reproduce anything you have there. i do suspect gtk3 has some issues - gtk3 windows do not change their appearance when they have foruse or not with CSD. this happens in e AND happens in good old fvwm. if gtk breaks in fvwm then it's gtk's fault. not to mention gtk insists on doing CSD even in fvwm so it looks visually broken anyway...
waaait. is this just the last release tarball or have you tried git for updates/fixes?
same story with sound recorder and about dialog or keyboard shortcuts dialog... i see nothing bad happening...
gedit with lots of terminals behind it ...
gedit here - so gtk3. preferences dialog...
here gimp is still gtk2 though. but:
<- see that. i did just what you described above. 3 windows. 2 terminals, 1 elm test. i minimize elm test. i bring it back with alt tab. i bound an extra mouse btn to winlist next or winlist show- doesn't matter - same result. i can bring it back - wheel work s (though why use wheel when you are going to click on it anyway?)
Jan 11 2022
does 7a674c6a29a408c6103bcc00c3bddee295fea07e fix it?
Jan 10 2022
Jan 2 2022
Dec 30 2021
resolved by 0fe3c751d1dbbd5bce89f7b437e0d2f0f2f36587