Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QgsSettings::beginGroup() is superior to QgsSettings::Section #25273

Closed
qgib opened this issue Nov 1, 2017 · 2 comments
Closed

QgsSettings::beginGroup() is superior to QgsSettings::Section #25273

qgib opened this issue Nov 1, 2017 · 2 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.

Comments

@qgib
Copy link
Contributor

qgib commented Nov 1, 2017

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.

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2019

Author Name: Giovanni Manghi (@gioman)


Please check if this issue is still valid on QGIS 3.4.5 or 3.6.


  • status_id was changed from Open to Feedback

@qgib qgib added Feedback Waiting on the submitter for answers Bug Either a bug report, or a bug fix. Let's hope for the latter! labels May 25, 2019
@github-actions
Copy link

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.

@github-actions github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Feb 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.
Projects
None yet
Development

No branches or pull requests

2 participants