feature request #7006
closed
Added by Patrick Plitzner over 6 years ago.
Updated about 6 years ago.
Assignee:
Patrick Plitzner
Description
This can be done with a copy of the plugin provided by OPCoach (https://github.com/opcoach/e4Preferences).
This might also give us the possibility to handle where and how preferences are stored.
Later on we should use Annotation to handle preferences (@Preference)
Files
- Description updated (diff)
- Description updated (diff)
- Description updated (diff)
- Status changed from New to Resolved
- Assignee changed from Patrick Plitzner to Katja Luther
- % Done changed from 0 to 50
- Status changed from Resolved to Closed
it takes quiet a long time to open the preferences, but it seems to work.
- Assignee changed from Katja Luther to Patrick Plitzner
- % Done changed from 50 to 100
The preferences often show up in the search result view (see attachement). This shouldn't be and is critical.
Added Katja to let her know that this is still an open issue.
Later on we should use Annotation to handle preferences (@Preference)
=> if not handled here but a good suggestion we should open a new ticket.
Andreas Müller wrote:
The preferences often show up in the search result view (see attachement). This shouldn't be and is critical.
Maybe related to #6990?
- Related to bug #7024: Preference pages are shown in editor parts added
the preferences could not be saved anymore or even worse once edit they where completely lost and could not be restored. this is fixed with Revision e8684498 and Revision a3c2ae78
Oh, I overlooked the position of the ':'
Thanks! Looks good.
- Status changed from Feedback to Resolved
- Assignee changed from Patrick Plitzner to Katja Luther
- % Done changed from 100 to 90
Please review if preferences are stored now.
- Status changed from Resolved to Closed
- Assignee changed from Katja Luther to Patrick Plitzner
- % Done changed from 90 to 100
Also available in: Atom
PDF
