You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BugEither a bug report, or a bug fix. Let's hope for the latter!FeedbackWaiting on the submitter for answersstaleUh oh! Seems this work is abandoned, and the PR is about to close.
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.
BugEither a bug report, or a bug fix. Let's hope for the latter!FeedbackWaiting on the submitter for answersstaleUh oh! Seems this work is abandoned, and the PR is about to close.
Author Name: Borys Jurgiel (@borysiasty)
Original Redmine Issue: 17376
Affected QGIS version: master
Redmine category:unknown
Assignee: Nathan Woodrow
Just a simple example:
QgsSettings settings;
settings.begingGroup( "my_group" );
settings.setValue( "my_key", 7, QgsSettings::Section::App )
results with:
@
[my_group]
app/key=7
@
Shouldn't beginGroup() optionally accept QgsSettings::Section? Like that:
@
void beginGroup( const QString &prefix, const QgsSettings::Section section = QgsSettings::Section::NoSection );
@
I marked it as a bug, as it causes rather unexpected results and makes beginGroup() more or less useless.
The text was updated successfully, but these errors were encountered: