Menu Editor 1.2 beta
- onemen
- Posts: 1136
- Joined: October 15th, 2004, 7:48 am
-
- Posts: 4019
- Joined: November 16th, 2003, 3:05 am
- Location: Russia, Moscow
Mozcerize, I'd rather not bump that thread. When we release next version, we'll change update.rdf and people will get the new version. Those who read this forum would find this thread already.
onemen, Some tree-related things have indeed changed on trunk (in June or July, iirc). So if you ask about 1.0->trunk transition problems, yes there were a few changes. Look up that bug and see. You can also see what changes I have done to menueditprefs.js to make it work on trunk (using mozdev's CVS web interface).
If you're asking about differences in recent trunk builds, I haven't noticed tree-related check-ins and I haven't yet had a chance to try 20050225 build.
btw, if this is not Menu Editor related, you should create a new thread and/or PM me.
onemen, Some tree-related things have indeed changed on trunk (in June or July, iirc). So if you ask about 1.0->trunk transition problems, yes there were a few changes. Look up that bug and see. You can also see what changes I have done to menueditprefs.js to make it work on trunk (using mozdev's CVS web interface).
If you're asking about differences in recent trunk builds, I haven't noticed tree-related check-ins and I haven't yet had a chance to try 20050225 build.
btw, if this is not Menu Editor related, you should create a new thread and/or PM me.
-
- Moderator
- Posts: 2037
- Joined: June 17th, 2004, 8:34 am
- Location: Manchester, England
- Contact:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050225 Firefox/1.0+
Firefox crashes when adding a separator in Menu Editor. (I don't like this trunk build at all so far, all hell appears to have broken loose.)
Firefox crashes when adding a separator in Menu Editor. (I don't like this trunk build at all so far, all hell appears to have broken loose.)
Last edited by manc39 on February 25th, 2005, 2:32 pm, edited 1 time in total.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060712 BonEcho/2.0b1
-
- Posts: 4019
- Joined: November 16th, 2003, 3:05 am
- Location: Russia, Moscow
-
- Moderator
- Posts: 2037
- Joined: June 17th, 2004, 8:34 am
- Location: Manchester, England
- Contact:
-
- Posts: 4019
- Joined: November 16th, 2003, 3:05 am
- Location: Russia, Moscow
Well, recent trunk builds are really messed up. Unless you're willing to crash all the time or you're an active core developer, I wouldn't recommend using 20050225. IMO, 20050218 is of decent quality, and then many changes landed that broke various parts of firefox (chrome registry rework, options window rework etc).
[edit]the crash problem is bug 283478
[edit]the crash problem is bug 283478
-
- Moderator
- Posts: 2037
- Joined: June 17th, 2004, 8:34 am
- Location: Manchester, England
- Contact:
I've been getting a new trunk building every couple of days, before this one I kept the previous build in a zip archive until the then current build was replaced and ready to be archived, then delete the older archive. Unfortunately the one time I need it I just deleted the old build completely Typical!
Anyway I'm straying slightly off topic there.
Anyway I'm straying slightly off topic there.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060712 BonEcho/2.0b1
-
- Posts: 6920
- Joined: July 29th, 2003, 1:09 pm
Oddity with xxx221: I have the Clusty Toolbar entries, such as "Search Web+ for" turned off in the Main Context Menu entry for the extension.
However, all four such entries keep showing up when I right-click on a page. If I go to the extension's options page, reenable any one of the four entries, then disable it again, all four entries disappear when I next right-click on a page.
However, all four such entries keep showing up when I right-click on a page. If I go to the extension's options page, reenable any one of the four entries, then disable it again, all four entries disappear when I next right-click on a page.
-
- Posts: 4019
- Joined: November 16th, 2003, 3:05 am
- Location: Russia, Moscow
-
- Posts: 6920
- Joined: July 29th, 2003, 1:09 pm
- GrailKnight
- Posts: 2359
- Joined: January 5th, 2004, 5:40 am
- Location: Pennsylvania, USA
-
- Posts: 4019
- Joined: November 16th, 2003, 3:05 am
- Location: Russia, Moscow
20050308
My attempt at fixing all these problems with dynamically modified menus: 20050308.
This may be less stable than previous versions. Do not install unless you're willing to help me with testing. (John, I hope that you will install this version though).
If it doesn't work, try changing menueditor.handleDynamicModifications temporary pref. To do this, go to about:config, right-click -> new -> integer.
This may be less stable than previous versions. Do not install unless you're willing to help me with testing. (John, I hope that you will install this version though).
If it doesn't work, try changing menueditor.handleDynamicModifications temporary pref. To do this, go to about:config, right-click -> new -> integer.
Code: Select all
menueditor.handleDynamicModifications
selects an approach to handling dynamic modification of menus:
0- do nothing
1- on popupshown check if the menu has changed
2- override DOM manipulation functions (appendChild etc). (default)
- onemen
- Posts: 1136
- Joined: October 15th, 2004, 7:48 am
ME 20050308
Code: Select all
menuedit: unexpected exception. dev. info follows:
QueryInterface=
function QueryInterface() {
[native code]
}
; message=Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIDOMXULElement.appendChild]; result=2147500035; name=NS_ERROR_INVALID_POINTER; filename=chrome://menuedit/content/menueditoverlay.js; lineNumber=210; columnNumber=0; location=JS frame :: chrome://menuedit/content/menueditoverlay.js :: anonymous :: line 210; inner=null; data=null; toString=
function toString() {
[native code]
}
; initialize=
function initialize() {
[native code]
}
;
- onemen
- Posts: 1136
- Joined: October 15th, 2004, 7:48 am