William Morder via tde-users wrote: > Did you put that header line, [General], before the lines for Show Menu > Bar & Show Status Bar? It seems like those headers might be important. > > And please disregard my lines of ###s, I just use that to set off quoted > text in an email when it is a very long passage. > > Every so often, I find that those snips taken from older config files > still work in the newer TDE releases. (I probably shouldn't say that; > those tricks might go away!) > > In any case, it *seems* like something like this ought to work, if only > you can find the right config file. There are also some with a different > extension, .kcfg, that I find in the newer releases, no longer plaintext > files but rather something like xml, maybe? In any case, I looked there: > /opt/trinity/share/config.kcfg > and on my machine (running Devuan Daedalus) there is no .kcfg file for > kate. Whether or not these can be modified by the ordinary user, I don't > know. But if so, it may be possible to write your own. There are .kcfg > files for other similar Trinity apps, such as kedit. > > I haven't yet tried to modify these, don't know if it's possible, but I > believe maybe there, or by changing lines in another such -rc file, your > hopes can at last be fulfilled, all your dreams come true. 1. regarding the location I am pretty sure the correct place is ~/.trinity (this was .kde3 before). 2. regarding the format K/TDE uses a simple text-based file format for all its configuration files. It consists of key-value pairs that are placed in groups. All KDE configuration files use UTF-8 encoding for text outside the ASCII range. The start of a group is indicated by a group name that is placed in square brackets. All the key-value entries that follow belong to the group. The group ends when either another group starts or when the end of the file is reached. Entries at the top of the file that are not preceded by a group name belong to the default group. https://userbase.kde.org/KDE_System_Administration/Configuration_Files 3. regarding changes in those config files. There must be corresponding code to read the value and use it in the code. As I am not aware of such options in Kate, I can only suggest to create feature request in TGW for extending Kate with this feature. In fact I think the showing of the toolbar when the app starts is hardcoded in Kate. 4. regarding the code behind The TQToolBar inherits TQDockWindows and we find following information TQMainWindow provides four dock areas (top, left, right and bottom) which can be used by dock windows. For many applications using the dock areas provided by TQMainWindow is sufficient. (See the TQDockArea documentation if you want to create your own dock areas.) In TQMainWindow a right-click popup menu (the dock window menu) is available which lists dock windows and can be used to show or hide them. (The popup menu only lists dock windows that have a caption.) https://www.trinitydesktop.org/docs/qt3/ntqdockwindow.html 5. In the case of Kate there are two XML UI files (I think at some point of time they received the extention .ui, but in this case it is ...ui.rc Anyway there is the gui - the things that you see /opt/trinity/share/apps/kate/kateui.rc /opt/trinity/share/apps/ktechlab/ktechlabkateui.rc I don't know what happens if you remove ToolBar from the XML. The code usually binds to those elements and provides standard or custom functionality. BR ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
