MonkeeSage, You shouldn't have to define the ViewManager stuff in K-Meleon. The original code just uses: if(m_panning) { nsCOMPtr<nsIScrollable> s(do_QueryInterface(mWebBrowser)); if (!s) return; Therefore I would guess you have to use do_QueryInterface, perhaps: if(m_panning) { nsCOMPtr<nsIViewManager> view(do_QueryInterface(mWebBrowse
Forum: General

MonkeeSage, I think frame autoscrolling can be implemented if you use the functions nsiScrollableView (view/public/nsIScrollableView.h) instead of nsIScrollable as is done currently. See the code here for the actual Mozilla scrolling functionality - http://lxr.mozilla.org/seamonkey/source/layout/html/base/src/nsPresShell.cpp#3258 - The functions are ScrollPage, ScrollLine, ScrollHorizontal, and
Forum: General

jsnj, Ok, that's a valid reason for it, I always thought of the go button as a dummies/newbies thing. Maybe you can use the pluginmsg macro function and send "findnick" to the bookmarks or hotlist plugin (favorites doesn't have findnick support). Hey if you know how the quicksearch nicknames are stored with the favorites in M$IE then the support can be added.
Forum: General

No. Really now, the go button ?!? The go button is ridiculous nonsense as is the go menu item or anything else starting with "go", "start", or "my". Stuff like this should be expunged from software everywhere. Just type or recall an address and press enter.
Forum: General

Since K-Meleon is working correctly for Japanese when run under the Japanese version of w98 then the same should be true for Chinese. While the browser supports Unicode for web page, the title bars, menu bars, and other OS elements really need the corresponding language version of the OS to display properly. Chuanhao Chiu do you have the Chinese version of w2k to test this with ?
Forum: Improvement requests

MonkeeSage, The called GetMenu function is in MenuParser.cpp and is defined to take a char * parameter but in BrowserFrm.cpp function Create and BrowserFrameGlue.cpp function ShowContextMenu, strings are passed with _T. Another really bad thing about c++, having multiple functions with the same name.
Forum: General

These are the prefs (true/false): kmeleon.plugins.bookmarks.chevron kmeleon.plugins.favorites.chevron kmeleon.plugins.hotlist.chevron
Forum: General

No, the policies only work on a domain basis. You can selectively enable or disable different aspects of Javascript though.
Forum: General

jsnj, Current versions of all three plugins (post 0.7.1) have the chevron dropdown (at least that's what I'm seeing in the code). MonkeeSage builds should have them. I agree it would be nice if toolbar buttons could open dropdown menus, I think MonkeeSage is looking into enabling the code to do that, most of the code is already there but commented out. See the thread "Is there a w
Forum: General

jsnj, I meant a vertical separator between the buttons. Basically the separator is itself a button but with no width, no height, and a special flag indicating it's actually a separator. I would guess there's some code somewhere that's adding one pixel for every button or something. Toolbar elements really shouldn't overlap. Note I don't really use the toolbars, I only h
Forum: General

Yes, see this doc - http://www.mozilla.org/projects/security/components/ConfigPolicy.html
Forum: General

jsnj, I know the separators code was added but never looked at, the big thing for me in the new toolbars.dll was being able to get rid of the annoying and stupid tooltips. The one line fix for bug 410 may have changed the overlap behavior. Does this also happen without using separators ? As for the separators, a quick look at the code doesn't turn up any problems. A button separator is adde
Forum: General

Maybe nsDocShellTreeOwner.cpp is part of webbrwsr.dll ?
Forum: General

MonkeeSage, The Mozilla 1.2.1 nsDocShellTreeOwner.cpp code is slightly different, the relevant section of code in routine ContextMenu was moved around for the fix. Based upon the change log for that file it should be possible to simply incorporate the current file into 1.2.1 and rebuild whatever dll (docshell.dll ?) it's part of.
Forum: General

MonkeeSage, Adding the required GetMenu function to Plugins.cpp is pretty easy, add GetMenu to the end of the kmeleonFunctions structure, a declaration in kmeleon_plugin.h, and the function itself is only a few lines: HMENU GetMenu(char *MenuName) { CMenu *menu = theApp.menus.GetMenu(MenuName); if (menu) return menu->m_hMenu; else return NULL; } The second block of
Forum: General

MonkeeSage, If you right click on the main logo on this page do you get a context menu in 1.4b - http://members.aol.com/AXCEL216/ As for getting an image context menu for the background image, once the Mozilla code is definitely working then the issue as to what context menu appears can be easily changed in K-Meleon.
Forum: General

Arual, You're just another idiot who doesn't understand software, I haven't made any "frillzy" as you put it changes. I fixed bugs and added useful functionality, I don't care about pretty graphics and stuff to help the clueless. About the documentation, funny it was enough that I was able to figure out how to make a dozen changes so far. Now what have you contribut
Forum: Improvement requests

MonkeeSage, There are several issues - one the functions in BrowserView.cpp which handle text editing call functions in a Mozilla clipboard interface (nsIClipboardCommands) which should ultimately call the same functions Mozilla does for the key defined in the xml files. Clearly something isn't right though because removing the ID_EDIT definitions from accel.cfg fixes bug 288. Also there�
Forum: General

MonkeeSage, About bug 323 - no context menu for images when there's a background image present - can you verify that this is still a problem in Mozilla 1.4a builds ? If not then forget this, if so then the problem seems to be in Mozilla file embedding/browser/webBrowser/nsDocShellTreeOwner.cpp, routine ChromeContextMenuListener::ContextMenu - it looks like once a background image is detect
Forum: General

MonkeeSage, I just noticed a pattern to bug 288 with form input fields sometimes being lost on back. This only seems to happen when text is pasted into a form input field, often the pasted text is lost when returning to the page via back. Text which is typed in or edited manually never seems to be lost. I tried removing the ID_EDIT_CUT, ID_EDIT_COPY, ID_EDIT_PASTE, and ID_EDIT_SELECT_ALL key def
Forum: General

MonkeeSage, As far as I can tell K-Meleon calls routines in Mozilla to handle the supported cut, copy, paste commands and Mozilla ultimately ends of calling clipboard routines. There would be have to an interface in Mozilla that K-Meleon could use for undo and redo that would allow them to be displayed on a menu but there isn't. Now the URL bar context menu works differently but I think tha
Forum: General

StefanTroll, Look here - http://gratisdei.com/KM.htm Now would you GET LOST you piece of crap dumbass - it's quite clear that you are a worthless troll and you have nothing to contribute to K-Meleon. If you like and want to use Phoenix then use it, nobody's stopping you but GO AWAY and stop bothering people here about it dumbass, you're not wanted here.
Forum: Development

MonkeeSage, There's commented out code in toolbars\toolbars.cpp which would allow menu items for toolbar buttons but I'm not sure if it's complete or if there are any issues. Definitely a question for the devs since there must be some reason it's commented out. Of course now that you know it's there you can uncomment it and try it. The only issue I can think of is that t
Forum: General

MonkeeSage, You're missing the fullscreen plugin, it was changed since the service pack.
Forum: General

One other thing, can you check if the English version of Mozilla displays extended characters correctly in the title bar to make sure it isn't some sort of build issue.
Forum: Improvement requests

There's a bug open for this issue (bug 226). Now Chuanhao Chiu reports that Chinese characters don't appear correctly in the title bar while Dave reports that Japanese characters do. Both languages require an extended character set and need to use Unicode so they should work (or not work) the same. The same is true for languages such as Hebrew as well. Please reconfirm, if title bar isn
Forum: Improvement requests

MonkeeSage, Looks good now, I like the separate links, they're conveinent for updates to only one component. By the way thanks for building all of many and sometimes frequent updates.
Forum: General

Al, You're absolutely right about that but too many people (dummies) simply don't want to read documentation and complain that software is too difficult to use and it's really annoying. This sort of crap leads to software being "dumbed down" which is something I am VERY much opposed to. Why shouldn't some software be written for techie audience for a change ?? Also
Forum: Improvement requests

MonkeeSage, The typos in mfcembed.rc for the statusbar messages are still there. The typos are in the string tables, in ID_EDIT_FINDNEXT and ID_EDIT_FINDPREV "occurence" is misspelled (a instead of e), in ID_VIEW_SOURCE "source" is misspelled (missing r). Here are the corrected lines: ID_EDIT_FINDNEXT "Find the next occurence of the specified text" ID_EDIT_FINDPRE
Forum: General

MonkeeSage, The list in AccelParser.cpp is only used for defining accelerators in accel.cfg so I seriously doubt any of the special Japanese keys would be used as accelerators since their purpose is as modifiers so it's safe to comment them out there, it won't affect their use elsewhere. Could you take the xp stuff out of the build you post separately ? I don't run xp (and never
Forum: General