The problem I talk about happens on kwrite, no kate. I get the crunch as well on kate. Cheers :)
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Jan 6 2019
Jan 5 2019
In D17730#382676, @cullmann wrote:
- Your comment to @zetazeta request ? I have tried to add a QScrollArea but without success :-/ Ideas? Perhaps is a second level of layout/widget needed(?)
I would not take care of that now but think about that in a separate request.
If we want that, perhaps one needs to think about having it scroll with the view, I don't think one wants a second scrollview.
Dec 26 2018
I don't know if it should be done in this revision but... I find it annoying that the status bar imposes a limit on the minimum width of the window.
Dec 8 2018
Guys this is great work. Can we please make the limits configurable? Each developer will have a different sweet spot. I don't want to burden this revision, maybe we can make a bug about configuring the limits and leave that part to someone confortable with the configs.
Nov 25 2018
In D17145#365759, @brauch wrote:It has often been discussed whether bug 398525 is actually valid, without real conclusion. Since the tabs do not show all documents, but only the n most recently used ones, it to me makes a lot of sense that new documents are added at the left, and then "drop off the shelf" towards the right if they are not being used, into the dropdown-menu.
Nov 24 2018
My bug is getting fixed! What a great community...
Nov 17 2018
Cconstructivist AI
Oct 14 2018
In D16169#342256, @zetazeta wrote:My use case: if I close a session with alt+f4, the next time I open it it will have the same files
There is already the option in kate for the session behaviour on startup (see settings -> configure kate -> sessions): start a new session, load the last used session, manully choose a session.
So your use case is already covered.
Oct 12 2018
In D16169#342247, @ngraham wrote:+1 for implementing the feature.
However, I'm always a bit wary about adding new off-by-default options. Making something optional in the first place is an a certain lack of confidence in the feature; having it off by default magnifies that. If this should really be both optional and off by default, should it really be done at all? My vote would be for turning it on by default, but I think ideally, this would be a global setting somewhere in System Settings (maybe the same place we'd put the options requested in https://bugs.kde.org/show_bug.cgi?id=376992) and would affect all KDE apps with tabs.