S60 Open to new features

When debugging your app in Carbide we will show your variables and their values so you can see how things are working. But there are some subtleties about which variables we show that can occasionally be confusing.

Carbide will usually show you the variables in a function that are live and in scope. That means we don’t show variables from other sub-scopes within the function: so if you have used a variable named “I” in multiple for-loops within a functions we will only show the one that is relevant. Also the compiler may reuse storage space for a local variable and the value won’t make any sense so we don’t show those either.

This normally works well but we’re only able to determine the list of relevant variables because if information left by the compiler. In some rare cases all of the compilers we use in Carbide can make mistakes and exclude variables that you want to see. To work around these miscues we added an option to show all of the local variables, even ones that may be redundant or confusing.

With this option on you will see all of the variables including the multiple “I”s and ones that may no longer have accurate values.