Return to Question

I have reached out to MMA SE and WRI to resolve the inability of Enterprise CDF to accept non-smooth functions as inputs. The former offered some suggestions , none of which were particularly helpful.and a support engineer at WRI informed me that my issue was forwarded to "the developers."

I have reached out to MMA SE and WRI to resolve the inability of Enterprise CDF to accept non-smooth functions as inputs. The former offered some suggestions , none of which were particularly helpful.and a support engineer at WRI informed me that my issue was forwarded to "the developers."

My issue with this workaround is that upon typing u[t], for example, in the entry box and thereafter hitting the Enter key, the expression u[t] is replaced by UnitStep[t]. I find this undesirable both aesthetically and functionally. So I ask, is a way to insure that the original expression u[t] remains in the entry box after entering it? One does not need to have an Enterprise version of MMA to test this as the issue is apparent from the nb code itself. Here is the code.

My issue with this workaround is that upon typing u[t], for example, in the entry box and thereafter hitting the Enter key, the expression u[t] is replaced by UnitStep[t]. I find this undesirable both aesthetically and functionally. So I ask, is there a way to insure that the original expression u[t] remains in the entry box after entering it? One does not need to have an Enterprise version of MMA to test this as the issue is apparent from the nb code itself. Here is the code.