Oxide

Use consistent naming for QFlags

Bug #1533223 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Fix Released
Low
Chris Coulson
Oxide branch-1.13

Bug Description

There is a recommended naming convention for QFlags types in the Qt documentation: http://doc.qt.io/qt-5/qflags.html. Ok, we don't need to use this exactly, but we should be consistent across our API. As I'd like us to provide headers so we have a C++ API, we should fix this up now in a way that doesn't break the QML API.

Chris Coulson (chrisccoulson)
Changed in oxide:
importance: Undecided → Low
status: New → Triaged
Chris Coulson (chrisccoulson)
Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
milestone: none → branch-1.13
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.