I understand this title may be a little confusing. From version 2.00 when the new classes feature was implemented, something became worse in LogCat and I will now explain. I have an intensive use of the Log because it's helps me track the execution flow of my apps. If I log an object from a class type, in addition to all variables from my class, references to all other modules appear.
Thus, I have very redundant objects = null which make it very difficult to find my real ones which have value <> null.
The biggest problem is that now I have more than 150 modules in my projects and these all make it difficult to me, to find what I am looking for in the Logs.
Enough theory, he is an example(the bold ones are my real values, the others are references to the modules which may be needed for this all to work but are truly not needed when debugging because they are always = null).
For the purpose of this quote, I will remove the original module names with random values, but you get the meaning. I will also copy the first 15 to all the rest to save some time.
Now, do you understand how hard is to find these values when looking at the logs? And this is a single object. Imagine this object being a variable inside another class. Then things get totally complicated!
Thus, I have very redundant objects = null which make it very difficult to find my real ones which have value <> null.
The biggest problem is that now I have more than 150 modules in my projects and these all make it difficult to me, to find what I am looking for in the Logs.
Enough theory, he is an example(the bold ones are my real values, the others are references to the modules which may be needed for this all to work but are truly not needed when debugging because they are always = null).
For the purpose of this quote, I will remove the original module names with random values, but you get the meaning. I will also copy the first 15 to all the rest to save some time.
[asfasf=null, asgasg=null, asasg2gasg=null
, hasgsag=null, gaswqr=null, asggasg=null
, module5=null, module6=null, module7=null
, module8=null, module9=null, module10=null
, module11=null, module12=null, module13=null
,asfasf=null, asgasg=null, asasg2gasg=null
, hasgsag=null, gaswqr=null, asggasg=null
, module5=null, module6=null, module7=null
, module8=null, module9=null, module10=null
, module11=null, module12=null, module13=null
,asfasf=null, asgasg=null, asasg2gasg=null
, hasgsag=null, gaswqr=null, asggasg=null
, module5=null, module6=null, module7=null
, module8=null, module9=null, module10=null
, module11=null, module12=null, module13=null
, zvisu=null, [B]p_help_item=[/B], zviewloader=null
, p_name=someProducts, p_target_activity=aProducts, ztrack=null
,asfasf=null, asgasg=null, asasg2gasg=null
, hasgsag=null, gaswqr=null, asggasg=null
, module5=null, module6=null, module7=null
, module8=null, module9=null, module10=null
, module11=null, module12=null, module13=null
, zsqll=null, zstatemanager=null, p_width=88
, p_top=141, p_left=488, p_height=97
, module5=null, module6=null, module7=null
, module8=null, module9=null, module10=null]
Now, do you understand how hard is to find these values when looking at the logs? And this is a single object. Imagine this object being a variable inside another class. Then things get totally complicated!
Last edited: