Ok... Recently I get a PC running Windows, Installed FF 2.0 and Tab effect. Tab efect don't work. Configuration:
Athlon 900
192MB RAM
nVidia GeForce2 MX400
Windows XP + DX9c
I figured out that FF didn't recognize/load the dynamic library with @wkwkrl.jp/humor/tab_effect;1 component.
I assume, you compiled the library for a particular procesor... like Pentium4, or AthlonXP. Please, check how you configured your compiler... I don't have an Idea how to do that under Win... I'm a linux user. Compile it for something general... like i686.
We could do many things with Tab effect... I would like to hepl port it for other platforms at first place... then we can bring general 3D rendering extension into mozilla applications (which I tried about a year before, but run out of time).
Ok, what do you thing about my resolution/suggestion and my offer?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I looked in to the project file... or what it is... and I didn't recognized any CPU type setting... Is it possible that Visaul Studio (I suppose you're usin VS) compiles binaries for exactly your CPU type? What CPU do you have?
And about the code... it's not bad, how long are you a programer?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I have to second the compiler options bug. My wife has it on her XP, and it looked cool. She is running on an Athlon XP processor. Me, I am running an Intel Laptop Pentium 4 Centrino. Tab Effect causes Firefox to die a quick and unexplained death just a fraction of a second after it becomes visible. If you tell Visual C to not use any optimizations, it should be able to produce a binary that works well for everyone.
Sure it could be all the other garbage I have installed in my Firefox... but since I don't see too much else posted here in the extension's forum, it's all I've got to go on.
Great addition to the Firefox on Windows family though! I will leave it in my extensions as disabled and hopefully there will be an update soon.
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok,
The extensions guid is {0784CD66-62FE-4cef-ABF4-F8ED9B654ACC}.
There will be a directory in your firefox profile directory with that name.
As it is installed on my machine using version 1.1, there are 2 subdirecories.
Content and Components.
By placing a copy of msvcr71.dll in the Components directory it works.
I am using version 7.10.3052.4 of that dll found I found in another extensions Components directory. Actually my computer had about 12 copies of this file, so a search of your computer should be faster than looking on the web for it. They were all the exact same size with differing dates. The file is 348,160 Bytes.
I did examine this projects dll files, and they appear to be all i386 specific, so I started hunting for a reason hers worked and mine didn't.
Her machine had no other extensions which also used msvcr71.dll, so a seach of her Firefox profile for msvcr71.dll came up empty. Otoh, my machine, my Firefox profile had 2 other extensions that used the same msvcr71.dll file and had that file included in their installation dir.
It would seem that when no other extension includes this file, maybe windows uses the one found in the C:\Windows\System32 folder. When one extension does include it, maybe all are required to include it. Who knows how windows goes about deciding to find a dll file?
Now that I have a browser working again, I thought I would let the author know my experience. Include the dll, in your package.
Best Regards,
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well I decided I needed a way to force all those extensions to use a common dll, even though that is also risky business. So I renamed them all to msvcr71.dll.save, and placed the dll in C:\Program Files\Mozilla Firefox. I could start Firefox with this arrangement. Since this is a windows only extension at present this doesn't matter so much, except maybe in some circumstances where users do not have write access to C:\Program Files\*.*
I have placed a notice on the addons.mozilla about this, and maybe that will help for now.
I would suggest making 2 xpi's for this extension. One with the dll, to be used if the user can't start his browser without using -safemode, as was my case.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok... Recently I get a PC running Windows, Installed FF 2.0 and Tab effect. Tab efect don't work. Configuration:
Athlon 900
192MB RAM
nVidia GeForce2 MX400
Windows XP + DX9c
I figured out that FF didn't recognize/load the dynamic library with @wkwkrl.jp/humor/tab_effect;1 component.
I assume, you compiled the library for a particular procesor... like Pentium4, or AthlonXP. Please, check how you configured your compiler... I don't have an Idea how to do that under Win... I'm a linux user. Compile it for something general... like i686.
We could do many things with Tab effect... I would like to hepl port it for other platforms at first place... then we can bring general 3D rendering extension into mozilla applications (which I tried about a year before, but run out of time).
Ok, what do you thing about my resolution/suggestion and my offer?
Hi, again!
I looked in to the project file... or what it is... and I didn't recognized any CPU type setting... Is it possible that Visaul Studio (I suppose you're usin VS) compiles binaries for exactly your CPU type? What CPU do you have?
And about the code... it's not bad, how long are you a programer?
Hi,
I think I have to second the compiler options bug. My wife has it on her XP, and it looked cool. She is running on an Athlon XP processor. Me, I am running an Intel Laptop Pentium 4 Centrino. Tab Effect causes Firefox to die a quick and unexplained death just a fraction of a second after it becomes visible. If you tell Visual C to not use any optimizations, it should be able to produce a binary that works well for everyone.
Sure it could be all the other garbage I have installed in my Firefox... but since I don't see too much else posted here in the extension's forum, it's all I've got to go on.
Great addition to the Firefox on Windows family though! I will leave it in my extensions as disabled and hopefully there will be an update soon.
John
Ok,
The extensions guid is {0784CD66-62FE-4cef-ABF4-F8ED9B654ACC}.
There will be a directory in your firefox profile directory with that name.
As it is installed on my machine using version 1.1, there are 2 subdirecories.
Content and Components.
By placing a copy of msvcr71.dll in the Components directory it works.
I am using version 7.10.3052.4 of that dll found I found in another extensions Components directory. Actually my computer had about 12 copies of this file, so a search of your computer should be faster than looking on the web for it. They were all the exact same size with differing dates. The file is 348,160 Bytes.
I did examine this projects dll files, and they appear to be all i386 specific, so I started hunting for a reason hers worked and mine didn't.
Her machine had no other extensions which also used msvcr71.dll, so a seach of her Firefox profile for msvcr71.dll came up empty. Otoh, my machine, my Firefox profile had 2 other extensions that used the same msvcr71.dll file and had that file included in their installation dir.
It would seem that when no other extension includes this file, maybe windows uses the one found in the C:\Windows\System32 folder. When one extension does include it, maybe all are required to include it. Who knows how windows goes about deciding to find a dll file?
Now that I have a browser working again, I thought I would let the author know my experience. Include the dll, in your package.
Best Regards,
John
Well I decided I needed a way to force all those extensions to use a common dll, even though that is also risky business. So I renamed them all to msvcr71.dll.save, and placed the dll in C:\Program Files\Mozilla Firefox. I could start Firefox with this arrangement. Since this is a windows only extension at present this doesn't matter so much, except maybe in some circumstances where users do not have write access to C:\Program Files\*.*
I have placed a notice on the addons.mozilla about this, and maybe that will help for now.
I would suggest making 2 xpi's for this extension. One with the dll, to be used if the user can't start his browser without using -safemode, as was my case.
Hi yinotaurus,
According to this post: https://sourceforge.net/people/viewjob.php?group_id=186816&job_id=27401
the project creator is already advertising for help wanted. I might donate some time to make surte this one "flies straight."
Best Regards,
John