Exception occurred in LoadCommandBars.

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hello.
Let me ask you a question on the subject.

The version I use is Xtreme Toolkit Pro v 18.6.0

If the command bar data registry saved in v16.4 that was used before is loaded in v18.6, an exception occurs in CXTPCommandBars :: LoadBarState inside LoadCommandBars and it is not loaded.

If the data is saved in V18.6, it will be read normally.
Does the CommandBar class require settings?

Registry save status:
Because the storage size of the command bar is large, the data body of the command bar is saved as a file in Zip.

Please let me know if there is a way to deal with this problem.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
taka Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 10 May 2017 Status: Offline Points: 7	Post Options Post Reply Quote taka Report Post Thanks(0) Quote Reply Topic: Exception occurred in LoadCommandBars. Posted: 02 March 2020 at 6:22am
	Hello. Let me ask you a question on the subject. The version I use is Xtreme Toolkit Pro v 18.6.0 If the command bar data registry saved in v16.4 that was used before is loaded in v18.6, an exception occurs in CXTPCommandBars :: LoadBarState inside LoadCommandBars and it is not loaded. If the data is saved in V18.6, it will be read normally. Does the CommandBar class require settings? Registry save status: Because the storage size of the command bar is large, the data body of the command bar is saved as a file in Zip. Please let me know if there is a way to deal with this problem.
	Taka Product: Xtreme Toolkit v 18.6.0 Platform: Windows 10 1909(64bit) Language: VC++ 2017 (15.9.20)