Is it possible to allow the use of the status bar via script, using a vbscript?
Joseph
Is it possible to allow the use of the status bar via script, using a
vbscript?
I have a script that deletes files in the temp folders and in IE 6 it would
use the status bar to display its progress.
Not so with IE7 which for "security" reasons prevents the status bar from
displaying anything unless the setting is changed in Tools -> Internet
Options, etc.
Does anyone know the registry key to modify for that?
Thanks in advance for your help.
Joseph
Sam Hobbs
this is something that Microsoft would provide a documented solution for.
Speaking of documentation .... guess what?
"Joseph" <josep...@hotmail.co.uk> wrote in message
news:51FC3BBA-E818-42F8...@microsoft.com...
mayayana
what you really want, see here:
http://support.microsoft.com/kb/182569
It looks like the value is probably 2103 set to 1.
With "Local Machine Lockdown" possible you actually
need to set the value in 4 places if you want to be
sure it's not being overridden by some other hidden
setting.
Where "***" = "Software\Microsoft\Windows\CurrentVersion\Internet Settings"
you would want to set the following:
HKLM\***\Zones\0\2103
HKCU\***\Zones\0\2103
HKLM\***\Lockdown_Zones\0\2103
HKCU\***\Lockdown_Zones\0\2103
Old Pedant
> I have a script that deletes files in the temp folders and in IE 6 it would
> use the status bar to display its progress.
> Not so with IE7 which for "security" reasons prevents the status bar from
> displaying anything unless the setting is changed in Tools -> Internet
> Options, etc.
Not to ask a dumb question, but...
Why not display the status in a <DIV> that you position right at the bottom
of the window? Just above the status bar?
That's easy to do. Here's a simple demo HTML page:
<html><body>
<div id="STATUS" style="position: absolute; width: 100%; height: 24px;
bottom:0px; color: white; background-color: black;"></div>
<form>
<input onchange='vbscript: document.getElementById("STATUS").innerHTML =
me.value' size=100>
</form>
</body></html>
Joseph
You answer is beautifully cryptic thanks - You wouldn't work for MS by any
chance?
Anyway I have read the doc on the msdn, the problem is not there its that I
have a script which relies on the status bar of a web page created at
run-time, which status bar is used to display run-time info to the user.
No way am I going to ask a user to go change their internet settings, too
complicated, trust me.
tada
"Sam Hobbs" <sam...@social.rr.com_change_social_to_socal> wrote in message
news:urBOE2N8...@TK2MSFTNGP04.phx.gbl...
Joseph
exactly what I was looking for, I'll check this out, thank you very much for
your help.
Joseph
"mayayana" <mayaX...@rcXXn.com> wrote in message
news:Ob6ptZO...@TK2MSFTNGP02.phx.gbl...
Joseph
though of that yesterday and in view of security issues amongst others, your
idea is probably the way ahead,
Thank you for your help, much appreciated.
Joseph
"Old Pedant" <OldP...@discussions.microsoft.com> wrote in message
news:C109F477-02FC-4886...@microsoft.com...
Old Pedant
> the problem is that it flickers so much it is nearly impossible to read
> what's in it.
You mean because you are changing the display so rapidly? And because it's
in a <DIV> it has to keep redrawing it?
If so, I'm surprised that the status line doesn't flicker, too.
I can think of a number of ways to try to reduce the flicker. One, of
course, is to *NOT* use inverse video. Just leaving the pseudo-status bar
the same color as the background should help a lot.
Might help to put a <SPAN> inside the <DIV> and just change the innerHTML of
the <SPAN>.
Could possibly put a "throttle" on that changing, so that changes aren't
displayed if they occur less than 50ms (or whatever number) after the prior
displayed one. That woudn't be hard.
Let's see...
<script>
var newStatus = "";
function updateStatus( )
{
document.getElementById("STATUS").innerHTML = newStatus;
setTimeout( "updateStatus( )", 100 );
}
</script>
And then do
<body onLoad="updateStatus( )">
and finally, instead of changing the innerHTML directly, have your code
simply dump the new messages into the
newStatus
variable. And then the timeout ensures that the display isn't updated more
than once every 100ms. So if the variable is updated more often, the
intermediate changes are just dropped into the old bitbucket.
Is that adequate?
Sam Hobbs
> "Joseph" wrote:
>
>> the problem is that it flickers so much it is nearly impossible to read
>> what's in it.
I don't see where Joseph wrote that; I looked and looked again and I cannot
find it. Is it because this is cross-posted so much?
Another solution is to store the status in a global variable after updating
the status and then if a new status text is the same as the current, don't
update the status bar text with it. It might be unlikely that new status
text is the same as current status text, but this is a simple optimization.
If it were me, I would pass the status text as an argument for the
updateStatus function.
Joseph
more careful next time.
Thank you to you and old pedant, your help is much appreciated.
Joseph
"Sam Hobbs" <sam...@social.rr.com_change_social_to_socal> wrote in message
news:#A0kKAo8...@TK2MSFTNGP02.phx.gbl...