- Регистрация
- 01.02.2012
- Сообщения
- 4 812
- Благодарностей
- 1 187
- Баллы
- 113
My view how logs should look like.
Problem:
There was some small improvements in logs, but this is far from what we need.
Now for handled actions there is not error, but warning. Ok that gives little bit clearly logs, but for us.
If we sell Zennobox to somebody they anyway thinking that there is some problems with bot. Because they do not understand Zenno logs system.
Other point where we need improvements is because it is not possible to debug in multithreads. Simple because you can not see difference in errors in zennoposter, only after copying Action ID. So if you have lot of errors then you can copy ID of one and that same action error 100 times, even if you are understood everything about this error. And actually even that not making clear picture about "if" actions, because for "if" actions there is not possible to copy any id nor is possible to find any in Zennoposter Progs Logs folder. Basically the only way to understand what "if" action made problems is to make snippet i will show below and add that to Bad end action to track "if" action errors.
Solution:
Option to disable logs in Zennoposter at all. Logs in Logs folder can leave as they is, but in Zennoposter they should be different.
In this case we can build up our own logs, for those who selling Zennobox this option would be the best.
Simple c# snippet will create logs for Zennoposter in case if they are disabled.
To make easiest debugging simple group Errors/Logs/Warnings with the same Action ID.
Like in picture. And you can copy Action id from line what gives the most problems and look in your project what you can improve.
I think those are the only improvements to make our life 100 times easier.
If anybody have any thoughts what more should be improved please post below.
Thanks
Problem:
There was some small improvements in logs, but this is far from what we need.
Now for handled actions there is not error, but warning. Ok that gives little bit clearly logs, but for us.
If we sell Zennobox to somebody they anyway thinking that there is some problems with bot. Because they do not understand Zenno logs system.
Other point where we need improvements is because it is not possible to debug in multithreads. Simple because you can not see difference in errors in zennoposter, only after copying Action ID. So if you have lot of errors then you can copy ID of one and that same action error 100 times, even if you are understood everything about this error. And actually even that not making clear picture about "if" actions, because for "if" actions there is not possible to copy any id nor is possible to find any in Zennoposter Progs Logs folder. Basically the only way to understand what "if" action made problems is to make snippet i will show below and add that to Bad end action to track "if" action errors.
Solution:
Option to disable logs in Zennoposter at all. Logs in Logs folder can leave as they is, but in Zennoposter they should be different.
In this case we can build up our own logs, for those who selling Zennobox this option would be the best.
Simple c# snippet will create logs for Zennoposter in case if they are disabled.
Код:
var error = project.GetLastError();
string comment = error.ActionComment;
string id = error.ActionId;
string groupId = error.ActionGroupId;
project.SendErrorToLog(error.ActionComment, "first action OwnCode C#");To make easiest debugging simple group Errors/Logs/Warnings with the same Action ID.
Like in picture. And you can copy Action id from line what gives the most problems and look in your project what you can improve.
I think those are the only improvements to make our life 100 times easier.
If anybody have any thoughts what more should be improved please post below.
Thanks
Последнее редактирование:
