i use API 0.9.5 in win32 & cocos2d-x.
Once I use SFS2X,my project have many Random errors,Most are pointer & vector. and UI display is not normal too(For example the word don't display and Image display is not normal)。
but i do not use SFS2X, local operation。UI display is normal ,and No Random errors。
too many Random errors i can't debug;
so How long will the next version release?
when release the next API???
Moderators: Lapo, Bax, MBagnati
Re: when release the next API???
Sorry this is not very clear.
Can you please provide the specific details of the errors you have found?
As regards the UI display I don't get it either. The API don't use any graphics/UI libraries of any type, ever. So I am not sure why you are correlating our API with those problems. More details are necessary, if you need us to help you.
Thanks
Can you please provide the specific details of the errors you have found?
As regards the UI display I don't get it either. The API don't use any graphics/UI libraries of any type, ever. So I am not sure why you are correlating our API with those problems. More details are necessary, if you need us to help you.
Thanks
Re: when release the next API???
Or cause the thread?
Re: when release the next API???
I meet the same problem. this is because the smartfox client api is dispatch events in background thread by default. you can't send the command to the cocos2d in the event handler,instead, you can make a command queue,that cocos2d can process in the main thread. Or you can make the smartfox client api in the threadsafe on, (g_pSmartFox->ThreadSafeMode(true);) and make a cocos2d shcheduler update. in the update, call the smartfox api's g_pSmartFox->ProcessEvents()
Re: when release the next API???
about the pointers in the apis:
why using the pointers. Using the value parameter is a good idea. i think the smartfox client api can make a copy of data from the client,not using the pointers from the client side,then the api side can using the memory pool to speed memory allocation! The speed penalty is very small,or can saved by using the memory pool.
why using the pointers. Using the value parameter is a good idea. i think the smartfox client api can make a copy of data from the client,not using the pointers from the client side,then the api side can using the memory pool to speed memory allocation! The speed penalty is very small,or can saved by using the memory pool.
Re: when release the next API???
why i turn on ThreadSafeMode,SFS2X Client is not work!!!
Code: Select all
m_ptrSmartFox->ThreadSafeMode(true);
Re: when release the next API???
you should call ProcessEvents() function in a update function. the smart fox dispatch the net messages in the ProcessEvents function
Re: when release the next API???
Currently we are working on API to improve usability (pointers usage) as required from users and to solve the risk of memory leaks.
To complete this review of API software we need of a little time, I think that the new version will be released in a couple of weeks.
It is not clear to me if you have found critical mistakes invoking the API into your project. If it is, please give me some details about the questions so I can try to investigate them.
To complete this review of API software we need of a little time, I think that the new version will be released in a couple of weeks.
It is not clear to me if you have found critical mistakes invoking the API into your project. If it is, please give me some details about the questions so I can try to investigate them.
Re: when release the next API???
Problem has been solved.
thanks balder!
thanks balder!
Who is online
Users browsing this forum: No registered users and 10 guests