On Tue, 4 Sep 2012 16:54:00 +0900 Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote:
> On Tue, 4 Sep 2012 10:20:35 +0300 (EEST) Robert Krambovitis > <rob...@split.gr> said: > > > > > > Generic E related: > > > > > - Annoying: When restarting E, any window that was maximised > > > > > with the "fill" > > > > > option is remembered as normal maximised. i.e. if I use the > > > > > "fill" > > > > > option to > > > > > tile windows to my liking, after restarting E, all those > > > > > windows will take up > > > > > the entire screen. > > > > > > > > ok. > > > > > > > > > - Obvious: Ability to set a threshold of screen size % above > > > > > which > > > > > the window > > > > > is considered "maximised", so when clicking the maximise > > > > > button, instead of > > > > > growing say 5 pixels, it will revert to a predefined > > > > > "unmaximised" > > > > > size. Or > > > > > at least after growing 5 pixels, and re-clicking, instead of > > > > > shrinking those > > > > > 5 pixels back, it will revert to said predefined size. > > > > > > > > not so simple. if the "normal" size is almost maximized... then > > > > e has > > > > no idea > > > > WHAT the normal size WAS - ever.e places a property on the > > > > window that > > > > survives a restart: __E_WINDOW_BORDER_SIZE and this holds the > > > > "normal" > > > > geometry. ie geometry before e did a maximize. if the geom > > > > before e did a > > > > maximize is almost maximized.. then what IS normal? e has zero > > > > clue. > > > > it doesn't > > > > know. > > > > > > normal could be theme defined, or configurable, i.e. a > > > configuration panel in which you define thresholds / defaults. > > > What I mean is that I have encountered many times when the > > > maximise button is essentially useless. > > > In some occasions I have encountered windows non full screen that > > > were full screen size so clicking the maximise button didn't > > > shrink/expand by a single pixel. > > > > > > > I think there's generally something going on with window size and > > state remembering. I think it's related to having multiple > > instances. i.e. I have 3 separate terminals running, which one will > > it remember ? so it remembers a large size and an unmaximised > > state, which combines into a useless maximise button on next start > > of E. Similarly, pidgin chat window and userlist get confused etc > > which may be what's happening with my "fill for tiling" issue. > > if the rememebred windows are not uniquely identifiable then its not > possible to remember them correctly. as such they much set properties > (name, class, role etc.) for this to be possible and these must be > DIFFERENT per window. A typical trick is to name the terminal windows on their title bar, each one with a different name. Some terminal programs let you do that. Then E17 can tell them apart based on the window name, and remember things differently for each one. How to set that up depends on which terminal program you use, a command line option, or an ANSI sequence echoed to the terminal. For pidgin, the role of the windows can be used. Pidgin has "conversation" and "buddy_list" as the windows roles for the ones you mentioned. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
