Pure Walt, from Concentrated Thought
Do your menu separators on Ext web applications suddenly appear as thick bars instead of thin lines? Here’s how to fix it.
I ran across a problem in Firefox 3.6.16 where my JavaScript applications produced with ExtJS were producing menu separators that were extra thick.
Even Ext demo pages did this: Menu Separator
Here’s how I solved it.
The problem can be addressed with the Web Developer add on.
Normally its Disable / Disable Minimum Font Size is checked. If it gets unchecked, Ext behaves very badly.
Check it and then reload the page; menu separators will be back to normal.
An amusement – notice how many of the Apple discussion threads report “2 Helpful, 1 Solved” and not only is the issue unsolved, but often there aren’t even three messages in the thread. Something’s broken, and apparently Apple doesn’t care.
I find it annoying that many of the the Apple Discussion Boards that I browse show “2 Helpful, 1 Solved” as the status to the message threads.
And it’s not that just it has this status wrong, but that often there aren’t even three messages total in the topic.
I’ve reported this problem to Apple in the past, but it’s been ignored for years.
The type ‘System.IObservable
During an upgrade of a C# WPF application that was using Reactive Extensions, I ran into this compile error:
The type ‘System.IObservable
exists in both ‘c:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll’ and ‘c:\Program Files (x86)\Microsoft Reactive Extensions\Redist\DesktopV2\System.Observable.dll’
This is roughly the same kind of Defined in Multiple Assemblies problem as I faced before. (Solution provided.)
In this case, the System.Observable.dll was pinned to the 3.5 release of the Reactive Extensions.
The solution was to:
Copy File
An unexpected error is keeping you from copying the file. If you continue to receive this error, you can use the error code to search for help with this problem.
Error 0x80070057: The parameter is incorrect.
SOLVED!
Went to copy a directory on Windows 7 from one drive to another, something that I had done quite frequently, even earlier that day.
However, this time, and nothing had changed substantially with the source files, I got an Error 0x80070057 message stating “The parameter is incorrect.” At that point the copy dialog from my simple drag and drop would allow me to retry (useless) or abort mid-copy.
The error message was unusually cryptic and less that helpful:
Copy File
An unexpected error is keeping you from copying the file. If you continue to receive this error, you can use the error code to search for help with this problem.
Error 0x80070057: The parameter is incorrect.
The disk was not full and a check disk revealed no errors.
THE SOLUTION
The destination directory name that I was copying into was pretty long, I basically had used a descriptive prefix, a date stamp of YYMMDDHHMMSS, by a space dash space, and a short descriptive comment. All in all it was about ~55 characters in length.
The directory I was copying from was a fairly deep structure.
That made me wonder if the fully qualified name of some directory path wasn’t exceeding some limit. On Windows, it appears to be 256 characters. On a Mac it appears to be 1023 characters.
Tricks aside, I was limited to the file system limits.
So, on the same disk, with the same files, immediately after yet-another-failure to copy, I renamed the destination folder to something considerably shorter and tried again.
Quick experimentation showed that was indeed the problem: the resulting path name formed during the copy was too long.
Solution: shorten the destination folder name and/or tighten up the path.