Use consistent naming for QFlags

Bug #1533223 reported by Chris Coulson on 2016-01-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Low
Chris Coulson

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.

Changed in oxide:
importance: Undecided → Low
status: New → Triaged
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  Edit
Everyone can see this information.

Other bug subscribers