cclog | high performance node.js logger | Command Line Interface library

You are probably running iOS 13 on the iPhone 11? You need only set up the main window and the rootViewController if running the app on a device with iOS 12 or earlier. With iOS 13, do not set up the main window and rootViewController.

You should check this at runtime. Something like:

I took the liberty to create a MCVE from your code.

x, y values are float

CCLOG("x: %f", value.x );

I though it was int

C++ is a compiled language meaning that you are not directly reading any source file at runtime. It doesn't matter if you change the source code when the application is running since you haven't compiled it.

One thing you could try is to use a scripting language and make it embedded in your c++. Then the player can script in that language and you can run the script.

The popular choice for scripting in a game is the LUA language.

I suggest you look at a book for writing games with C++ such as Game Coding Complete, Fourth Edition

0xCCCCCCCC, a typical value used to fill uninitialized memory in Debug builds, interpreted as a 32-bit float, equals -107374176.000000. You're printing an uninitialized float value.

I tested your code and I could create the data table.

It doesn't look like you're calling moveTo, which is the BannerView method that changes the banner's position. There's a version that takes the constant you mentioned (kPositionBottom), and a version that takes an (x,y) pair.

CCLOG or cocos2d::log uses the Visual Studio's Debug windows, which is different to write to console where std::cout works.

Therefore, there are two ways to get rid of your problem: writing to console using std::cout or writing to output windows using different methods than CCLOG

First choice, you have to change your project type from Win32 Application Project to Win32 Console Project. This is kind of going around with Visual Studio stuffs, and in most cases, your project is created automatically via cocos2d's console. You can see this post. I'm not recommend this way IMO.

Second choice, use your own code to write to output which discussed here.

There is another way that you can use std::string and std::ostringstream to "print" your variables to buffer, and then just print your string to output windows via CCLOG

CCLOG is a little bit wrapping the code to make it convenience where we log resources checking, errors, file processing, etc which usually occur when run time. If not in those cases, you should probably set break points to view what the values are instead.

Edited: Since you chose the second approach, I would recommend using std::ostringstream than sprintf, and using CCLog instead of OutputDebugString (because you just print it out and independent OS, no need extra arguments)

Here is an example code:

The documentation does not tell this, but the programmers-guide does: