Anonymous (192.55.52.x) 15 May 2008 18:57
I downloaded version 1.2.2.1 from this website, as well as QT Breadcrumbs Address Bar. If I then go into IE7 and right click on the tool-bars, I have the option to enable the QT Tab bar. (Standard Buttons cannot be enabled - nothing is shown, same with breadcrumb toolbar) When I enable iQT Tabs in IE7, and then create groups in Win Explorer which contain web pages, when they load they create havoc (esp. sites heavy with JS and Frames). Among other things it asks me if I want to close all the tabs (Before anything is really loaded). It seams to first load everything to the IE7 tabs, then QT Tabs attempt to close them and open new tabs with the same location. Some times I find a tab open in QT Tabs which have been opened in this way with some odd HTML file like "NoHover.htm" or whatever. (?) Below I have copied another error I get when a particular URL is too long for QT Tabs to handle it properly. I think until these issues are addressed, users of IE7 are better off not activating the QT Tab toolbar, and not setting up groups which contain web content. I think I like and prefer all the options that QT Tabs offer me in Windows explorer, and I would like the same or similar ability when browsing in IE7. I don't know if underneat it all, maybe IE and Windows Explorer are really the same engine, and cannot have toolbars added in one without the other. If you can build it, I would really like to see your take on tabbed browsing for IE. I think M$ missed the boat on that design (FF does it better than M$), and I think this would be a natural next-step for you to also extend internet browsing usability and options.
Thanks for all the work on these fine tools.
System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
at System.IO.Path.GetDirectoryName(String path)
at QTTabBarLib.QTTabBarClass.OpenNewTab(IDLWrapper idlw, Boolean blockSelecting, Boolean fForceNew)
at QTTabBarLib.QTTabBarClass.OpenNewTab(String path, Boolean blockSelecting)
at QTTabBarLib.QTTabBarClass.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
**** Loaded Assemblies ****
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINNT/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
QTTabBar
Assembly Version: 1.0.0.0
Win32 Version: 1.2.2.1
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/QTTabBar/1.0.0.0__78a0cde69b47ca25/QTTabBar.dll
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
QTPluginLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.2
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/QTPluginLib/1.0.0.0__78a0cde69b47ca25/QTPluginLib.dll
FolderTreeButton
Assembly Version: 1.0.0.0
Win32 Version: 1.2.2.1
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/QTTabBar/1.0.0.0__78a0cde69b47ca25/QTTabBar.dll
Interop.SHDocVw
Assembly Version: 1.1.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/Interop.SHDocVw/1.1.0.0__78a0cde69b47ca25/Interop.SHDocVw.dll
**** JIT Debugging ****
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
