FreeTextBox (http://www.freetextbox.com/demos/) does not work in Firefox 17. What has changed?
FTB works correctly in previous Firefox versions and in all versions of other browsers.
(FreeTextBox develop has been terminated: "Please note that FreeTextBox has been discontinued. You may still purchase the software, but it is considered unsupported.")
Any idea?
Thanks.
Resolved. Problem was, the FTB anticipates value in the userAgent string part "Gecko/date", which then parses, creates a date object and compares if the returned date is greater than that which is permitted. However, because the value that Firefox now 17 uses, is changed to "Gecko/17.0", an exception occurs and the variable isMozillaEditor is not assigned value to true (this is done in the file BrowserInfo.cs). Therefore, the FTB does not start.
Related
We have to use VBScript as an embedded script engine in our Hospital Information System.
When we use nothing to set the value of a control (textbox/checkbox/...) it worked always fine. Since somepoint it sets now the textbox to "?>".
item("TEXTBOX").value = nothing ' Leads to -> "?>"
It is not completly clear what causes this, maybe a windows update is responsible, every rollup ~ since KB3212646 Win7 2017-01 seems to cause this error.
My Question is now, has someone else also seem this error, so that it is clear that MS causes this error or is our HIS publisher responsible for not handling nothing correct.
I know setting a textbox to Nothing is not best practice instead "" should be better, but since the item object could be more the just a textbox e.g. a combobox/checkbox this seems, from an objectoriented perpsective, better. Or am I completly wrong?
Following #Ansgar comment, you should apparently change everywhere you have = nothing to = "" in your example
item("TEXTBOX").value = ""
Beware to keep the nothing if you have the Set keyword in left
Set some_object = Nothing
Using a standard VBScript Randomize statement (below) which works fine -- most of the time.
...RANDOMIZE (Cbyte(Left(Right(Time(),5),2)))
RANDOMIZE...
It took a bit, but in digging thru log files, I've noticed that it throws this 500 error:
Type mismatch: 'Cbyte'
when the users' languages are non-English.
I tried changing the Session.LCID (I'm using Classic ASP) in a test page but no effect.
Any suggestions for fixing or a work-around? Thank you...
It appears you're trying to randomise based on the seconds-within-the-minute value:
12:34:56 AM
|---|
56 AM (right(5))
||
56 (left(2))
Now I have no idea of the top of my head what Time() would return in a Spanish locale, but it may well be something like 12:34:56 de la mañana.
What I do know is that relying on a specific presentation format in a globalised world is a bad idea. In your case, it may involve trying to convert left(right("12:34:56 de la mañana",5),2), or "añ", into a numeric value, something it's not going to be happy with.
If you want a true root cause analysis, I'd suggest catching the conversion error and actually logging what Time() is presenting itself as when it errors.
If you just want to fix it, find a way to get the seconds that doesn't depend on locale, for example:
secs = Second(Time())
As an aside, I'm not sure why you think this is even needed. The documentation for the VBScript Randomise function states that, if an argument is not given, the value returned by the system timer is used as the new seed value. Hence it's already based on the current time.
I wrote code in SQL Server that gives the year, the month and some data for those months in separate columns. The column for month (MM) gives months in numeric digits (1 to 12).
The code I used was:
Select ....
,Month(IRDate) AS MM
,...
I created a report in MS VS Report builder and included all the data in table columns. The report runs fine. However, at the bottom I get the below warning message:
[rsInvalidFormatString] The Format value for the textrun
‘MM.Paragraphs[0].TextRuns[0]’ is not valid. Format specifier was
invalid.
I checked the formatting for that cell, it is set to default - No formatting.
In the report, I've set the parameter to have a default value as
=DateValue("September 01, 2016")
Would that be the issue? Maybe the default value is not the right format? I removed the default value and kept it as no specified value. Warning message still comes up.
How can I fix this?
Have you tried formatting the textbox properties that holds the MM value to be a number datatype with no decimal places?
Regarding your other question about the default parameter value, I have typically seen DateValue formatted as such: 9/1/2016
Also, is your parameter datatype set to Date/Time?
Apparently, the error message '[rsInvalidFormatString] The Format value for the textrun....' is a log message. Rectifying the problem does not take away the message because it is a log message. So even after you correct the issue, the message will still show.
The only way to remove that message is to simply restart Visual Studio. When Visual Studio starts back up, the log is cleared and you won't see the message any more.
"Who knew healthcare would be so complicated?" ;)
Gah...this upgrade to ColdFusion 11 continues to give me massive headaches!!! I encountered a couple of issues today with CFChart.
First...I used to be able to have the $$ variables in lower case..that no longer works. The documentation says camelCase works, but that still produced an error. Upper case though, thankfully, works.
Second, the values in the $$ variables seem to have gotten all screwed up...
I had this code in CF10 (and CF9, CF8 etc....)
<cfchart format="#myformat#"
chartheight="350"
chartwidth="600"
show3d="yes"
showlegend="yes"
pieslicestyle="sliced"
xaxistitle="RELATED_TO"
yaxistitle="NBR"
url="chart_rpt.cfm?value=$value$&item=$itemlabel$&series=$serieslabel$&rptpd=#rptpd#&rpttype=#rptval#">
<cfchartseries
type="pie"
query="appdata"
itemcolumn="related_to"
valuecolumn="nbr"
serieslabel="Type"
>
</cfchartseries>
</cfchart>
I had to change this to (charts look identical, by the by...):
<cfchart format="#myformat#"
chartheight="350"
chartwidth="600"
show3d="yes"
showlegend="yes"
pieslicestyle="sliced"
xaxistitle="RELATED_TO"
yaxistitle="NBR"
url="chart_rpt.cfm?value=$VALUE$&item=$SERIESLABEL$&series=$ITEMLABEL$&rptpd=#rptpd#&rpttype=#rptval#" >
<cfchartseries
type="pie"
query="appdata"
itemcolumn="related_to"
valuecolumn="nbr"
serieslabel="Type"
>
</cfchartseries>
</cfchart>
Note the change in the url clause: The value in $SERIESLABEL$ should be 'Type'...instead its 'Foreign'. The value in $ITEMLABEL$ should be 'Foreign' but instead is 'Type'. I had to switch the $$ variables around for the chart_rpt.cfm routine to produce the expected data.
Did they change the definitions of these $$ variables? Is anyone else having these issues?
I am crossfading some audio and I have a equal power curve stored in a table. I'm calling this function to start the fadeout. The fade parameter is a GainNode made with createGain()
fade.gain.setValueCurveAtTime(epCurveOut, context.currentTime, fadeTime);
In Chrome and Safari all goes well, but Firefox (v30) complains:
SyntaxError: An invalid or illegal string was specified
Instead of context.currentTime I've tried 0 and 0.01. Is this method not implemented maybe? If so how would I alternatively schedule a cosine equal power ramp over time?
This seems to be a bug on our end indeed, I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1069825 to track this.
Firefox seems to give that error whenever it doesn't like the parameters to setValueCurveAtTime. For example, if epCurveOut is an empty Float32Array, or if there is already a parameter change scheduled at the same time. I suspect the latter, because Chrome doesn't throw an error under the same circumstances. For example:
curve = new Float32Array([0.5, 0.5]);
node.gain.setValueCurveAtTime(curve, 5, 1);
node.gain.setValueCurveAtTime(curve, 5, 1);
Firefox throws the error the second time. Chrome doesn't throw an error. If you call node.gain.cancelScheduledValues(5) in between the calls to setValueCurveAtTime, Firefox allows it.
EDIT: Oh, hmm, Chrome doesn't complain about an empty Float32Array either. Well, anyway, Firefox seems to be much less forgiving, and gives that error when the arguments' types are correct but the values aren't allowed.