Dear list, I think that (show-fps 1) used to show the fps independently of showing the code. Now it is affected by ctrl+h.
Is this a intentional change? The downside to this is that showing the code takes some resources and effects the fps so now we are unable to benchmark without including the -slight- cost of showing the code. How about this; (show-fps 0) => off (show-fps 1) => current behaviour (show-fps 2) => old behaviour of showing the fps regardless of the status of the code visibility Maybe there is some other issue, for example me being confused by something; I don't remember anything about this being changed so perhaps it's a accident or perhaps I'm the only one who sees a slight downside. If I'm the only one then maybe it's not worth the fix. Yours, Kas.
