Find the Best Demos and Examples

Check out this quick tour to find the best demos and examples for you, and to see how the Felgo SDK can help you to develop your next app or game!

Forums

OverviewFelgo 1 Support › Disable intern Console Output

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #6252

    florian.kieninger

    Hello,

    how to disable these console-outputs?

     

    cocos2d : getActionByTag: Target not found

    cocos2d : getActionByTag: Target not found

    cocos2d : getActionByTag: Target not found

    cocos2d : getActionByTag: Target not found

    SpriteSequence: jumpTo() called for stand

    CCAnimatedSpriteManager: this sprite changed its running property: Sprite_QMLTYPE_31(0x228eaf18)

    …….

    CCAnimatedSpriteManager: this sprite changed its running property: Sprite_QMLTYPE_31(0x228eaf18)

    CCAnimatedSpriteManager: this sprite changed its running property: Sprite_QMLTYPE_31(0x228eaf18)

    CCAnimatedSpriteManager: for this sprite no action exists – this happens when frameCount is 1

    SpriteSequence: jumpTo() called for stand

    CCAnimatedSpriteManager: this sprite changed its running property: Sprite_QMLTYPE_31(0x228eaf18)

    CCAnimatedSpriteManager: this sprite changed its running property: Sprite_QMLTYPE_31(0x228eaf18)

    CCAnimatedSpriteManager: for this sprite no action exists – this happens when frameCount is 1

    cocos2d : getActionByTag: Target not found

    cocos2d : getActionByTag: Target not found

    cocos2d : getActionByTag: Target not found

    cocos2d : getActionByTag: Target not found

     

    It’s impossible to read our own outputs….

     

    Grettings,

    Florian

    #6256

    Christian
    Felgo Team

    Hi Florian,

    the engine output cannot be disabled in the debug build of the games in the current version. However, you can add a prefix to your custom log outputs like “__” so your outputs are better visible in the debug output, or you can also then search the debug output for your prefix so you will find your custom outputs one by one.

    Cheers, Chris

     

    #6257

    Michael

    I’ve also noticed there are so many incidental messages in the Application Output of Qt Creator that it’s hard to locate your own. It’s a good idea to prefix messages, but in future it would be good to have a way to filter out these other messages, so only your own console.debug message come through. On another system I’ve noticed there is a ‘message level’ setting where you can progressively filter out messages based on importance. Alternatively I wonder if it’s possible to add another output pane for just V-play user’s own console messages (or similar)?

    #6258

    Christian
    Felgo Team

    Hi Michael,

    turning off the engine output is on our roadmap together with a more flexible logging system, thanks for bringing this up! Currently the best way to filter is by prefixing and then using the search functionality in the output pane.

    Cheers, Chris

    #6260

    Martin

    I’d just like to express my support for this request (as also noted in the roadmap thread some months ago). The output is pretty cluttered with internal and application messages. A filtering system like in the common logging libraries would be really helpful. It does not have to be too sophisticated though.

    Cheers, Martin

Viewing 5 posts - 1 through 5 (of 5 total)

RSS feed for this thread

You must be logged in to reply to this topic.