3 deleted 10 characters in body
source | link

I have found a workaround by defining, for example,

u[z_] := UnitStep[z];
abs[z_] := Abs[z];

in the Initialization section. Upon exporting to Enterprise CDF, I can, for example, type u[t] in the entry box and get the desired slope field.

Regrettably, this workaround does have a flaw: upon typing u[t] in the entry box and then hitting the Enter key, the expression u[t] is replaced by UnitStep[t]. I want 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. I don't know how to code this property into my nb file. Perhaps I shouldShould post this question as a new one.?

I have found a workaround by defining, for example,

u[z_] := UnitStep[z];
abs[z_] := Abs[z];

in the Initialization section. Upon exporting to Enterprise CDF, I can, for example, type u[t] in the entry box and get the desired slope field.

Regrettably, this workaround does have a flaw: upon typing u[t] in the entry box and then hitting the Enter key, the expression u[t] is replaced by UnitStep[t]. I want 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. I don't know how to code this property into my nb file. Perhaps I should post this question as a new one.

I have found a workaround by defining, for example,

u[z_] := UnitStep[z];
abs[z_] := Abs[z];

in the Initialization section. Upon exporting to Enterprise CDF, I can, for example, type u[t] in the entry box and get the desired slope field.

Regrettably, this workaround does have a flaw: upon typing u[t] in the entry box and then hitting the Enter key, the expression u[t] is replaced by UnitStep[t]. I want 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. I don't know how to code this property into my nb file. Should post this question as a new one?

2 edited body
source | link

I have found a workaround by defining, for example,

u[z_] := UnitStep[z];
abs[z_] := Abs[z];

in the Initialization section. Upon exporting to Enterprise CDF, I can, for example, type u[t] in the entry box and get the desired slope field.

Regrettably, this workaround does have a flaw: upon typing h[t]u[t] in the entry box and then hitting the Enter key, the expression h[t]u[t] is replaced by UnitStep[t]. I want 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. I don't know how to code this property into my nb file. Perhaps I should post this question as a new one.

I have found a workaround by defining, for example,

u[z_] := UnitStep[z];
abs[z_] := Abs[z];

in the Initialization section. Upon exporting to Enterprise CDF, I can, for example, type u[t] in the entry box and get the desired slope field.

Regrettably, this workaround does have a flaw: upon typing h[t] in the entry box and then hitting the Enter key, the expression h[t] is replaced by UnitStep[t]. I want 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. I don't know how to code this property into my nb file. Perhaps I should post this question as a new one.

I have found a workaround by defining, for example,

u[z_] := UnitStep[z];
abs[z_] := Abs[z];

in the Initialization section. Upon exporting to Enterprise CDF, I can, for example, type u[t] in the entry box and get the desired slope field.

Regrettably, this workaround does have a flaw: upon typing u[t] in the entry box and then hitting the Enter key, the expression u[t] is replaced by UnitStep[t]. I want 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. I don't know how to code this property into my nb file. Perhaps I should post this question as a new one.

1
source | link

I have found a workaround by defining, for example,

u[z_] := UnitStep[z];
abs[z_] := Abs[z];

in the Initialization section. Upon exporting to Enterprise CDF, I can, for example, type u[t] in the entry box and get the desired slope field.

Regrettably, this workaround does have a flaw: upon typing h[t] in the entry box and then hitting the Enter key, the expression h[t] is replaced by UnitStep[t]. I want 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. I don't know how to code this property into my nb file. Perhaps I should post this question as a new one.