https://bugs.kde.org/show_bug.cgi?id=299526
Albert Astals Cid <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Albert Astals Cid <[email protected]> --- That's a quick and dirty solution but not really optimal since you have no access to the settings headers so you are stuck with the default options that might not suit you. The solution I would like is make it so that the user of the library can create it's own settings instance, the problem is that settings now mixes things used in core like the memory and things used in the ui like should show the sidebar or not. What do you think about splitting the current settings into CoreSettings and UISettings and then installing the CoreSettings headers? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Okular-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/okular-devel
