{"id":4234,"date":"2022-02-07T15:57:30","date_gmt":"2022-02-07T15:57:30","guid":{"rendered":"http:\/\/truelogic.org\/wordpress\/?p=4234"},"modified":"2022-02-07T15:57:31","modified_gmt":"2022-02-07T15:57:31","slug":"13d-wxwidgets-wxconfig-usage","status":"publish","type":"post","link":"https:\/\/truelogic.org\/wordpress\/2022\/02\/07\/13d-wxwidgets-wxconfig-usage\/","title":{"rendered":"13d. wxWidgets – wxConfig Usage"},"content":{"rendered":"\n

OVERVIEW<\/strong><\/p>\n\n\n\n

The purpose of config classes in wxWidgets is to store various information and data which can be retrievable later on. Config data can be stored in a hierarchical manner much like a directory system.<\/p>\n\n\n\n

Depending on the underlying platform, configuration data is stored in different ways. For eg.in Linux and Unix, they are stored as files in the disk and in Windows they are stored as keys in the Windows registry. wxWidgets provides an abstract class called wxConfigBase<\/em> which is then implemented as wxFileConfig<\/em> and wxRegConfig<\/em>.<\/p>\n\n\n\n

To make things easy, there is a class called wxConfig<\/em> which automatically works with wxFileConfig<\/em> and wxRegConfig<\/em> as required, thus saving you the trouble of dealing with file systems and Windows registry. <\/p>\n\n\n\n

In the sample code below, we write some values to wxConfig<\/em> in a hierarchy. When we load the application with a command line parameter read<\/em>, it reads the values back from the wxConfig<\/em> system. Note that the delete config <\/em>statement is what saves all the values to the wxConfig system. Without that line, nothing would be saved.<\/p>\n\n\n\n

SAMPLE CODE<\/strong><\/p>\n\n\n\n

config-usage.cpp<\/pre>\n\n\n
\n#include  <wx\/wxprec.h>\n#ifndef WX_PRECOMP\n\t#include <wx\/wx.h>\n#endif\n#include <wx\/config.h>\n#include <wx\/string.h>\n\n\nint main(int argc, char **argv) {\n\twxInitialize();\n\twxConfig *config = new wxConfig("myapp");\n\n\tif (argc >= 2) {\n\t  wxString arg = argv[1];\n\t  if (arg == wxT("read")) {\n\t    wxPuts(config->Read(wxT("Key 1")));\n\t    wxPuts(config->Read(wxT("Key 2")));\n\t    wxPuts(config->Read(wxT("Key 3")));\n\t    \n\t    config->SetPath("\/folder1");\n\t    wxPuts(config->Read(wxT("Folder1Key")));\n\n\t    config->SetPath("\/folder1\/folder11");\n\t    wxPuts(config->Read(wxT("Folder11Key")));\n\t  }\n\t  return 1;\n\t}\n\tconfig->Write(wxT("Key 1"), wxT("Value 1"));\n\tconfig->Write(wxT("Key 2"), wxT("Value 2"));\n\tconfig->Write(wxT("Key 3"), wxT("Value 3"));\n\n\tconfig->SetPath("\/folder1\/folder11");\n\tconfig->Write(wxT("Folder11Key"), wxT("Value in folder 11"));\n\tconfig->SetPath("\/folder1");\n\tconfig->Write(wxT("Folder1Key"), wxT("Value in folder 1"));\n\n\n\tdelete config;\n\twxPuts(wxT("done"));\n\twxUninitialize();\n}\n\n<\/pre><\/div>\n\n\n
The output is given below<\/p>\n\n\n\n
\"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"
OVERVIEW The purpose of config classes in wxWidgets is to store various information and data which can be retrievable later on. Config data can be […]<\/a><\/p>\n<\/div>","protected":false},"author":1,"featured_media":3595,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[302,365],"tags":[],"class_list":["post-4234","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cc","category-wxwidgets"],"_links":{"self":[{"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/posts\/4234","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/comments?post=4234"}],"version-history":[{"count":5,"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/posts\/4234\/revisions"}],"predecessor-version":[{"id":4240,"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/posts\/4234\/revisions\/4240"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/media\/3595"}],"wp:attachment":[{"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/media?parent=4234"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/categories?post=4234"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/truelogic.org\/wordpress\/wp-json\/wp\/v2\/tags?post=4234"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}