Changes

Jump to: navigation, search

Mouse Lock Implementation FAQ

4,973 bytes added, 14:56, 6 December 2011
Blur a window on a mochitest
Afterwards, you can freely clone the repository and the build should now work.
===Greg: How do I resolve the error where CL cannot be found?===this This is the error that comes up:
'''checking whether the C compiler (cl ) works... no
the correct batch file and if you get this error check the path in the file to make sure it goes to the right place.
===Greg: How do I resolve the atlbase.h being missing?=== 
While running the make command, you get an error saying that atlbase.h file is missing!
===After building a debug version of Firefox on Windows, should I be seeing a lot of WARNING messages?===
After a successful build, I launched Firefox Nightly, I got a command prompt screen that started outputting messages. Many of them are warning messages, should I be worried?Also, certain warnings (assertions) causes pop ups that need to be dealt with, is there a way to get rid of that? '''Answer 1''': No, the warning messages are normal. If you're using command prompt to start firefox.exe, you can type:<pre>set XPCOM_DEBUG_BREAK=warn</pre>NOTE: in a BASH shell you usually have to do it this way:<pre>export XPCOM_DEBUG_BREAK=warn</pre>That should suppress all pop ups. This is only necessary for windows. Mac and Linux machines should be set to this by default. ===Can't find header GL/glx.h for WebGL=== While running make, the following error presents itself:<blockquote>configure: error: Can't find header GL/glx.h for WebGL (install mesa-common-dev (Ubuntu), mesa-libGL-devel (Fedora), or Mesa-devel (openSUSE))) </blockquote>'''Answer 1''': This error is most likely caused by an error in your .mozconfig file. Make sure that all commands are prefixed properly with their correct add command (mk_add... or ac_add...) ===LNK 1210 Error=== While running make, the following error presents itself:<blockquote>LINK : fatal error LNK1210: exceeded internal ILK size limit; link with /INCREMENTAL:NO</blockquote>'''Answer 1''': This error is most likely caused by VC's incremental linking reaching its hard coded limit. To fix the problem, edit your '''config.in''' and locate the line #2505 find the following section of code, and insert '''-INCREMENTAL:NO''' options into LDFLAGS flag.
<pre>if test $_MSC_VER -ge 1400; then LDFLAGS=”$LDFLAGS -LARGEADDRESSAWARE -NXCOMPAT -INCREMENTAL:NO“ dnl For profile-guided optimization PROFILE_GEN_CFLAGS=”-GL” PROFILE_GEN_LDFLAGS=”-LTCG:PGINSTRUMENT”</pre> ===How to pull new changes for mouselock=Discussion=='''NorthWind871. Copy the repo URL in git hub <br />2. git remote add <repo name> git:''' With regard //<url> <br />3. git checkout master, pull to master first to avoid conflict <br />4. git pull <repo name>/master <br />5. git checkout mouselock, change to mouse lock to merge with our up to date master. <br />6. git merge master <br /><br />To fix a merge conflict <br />1. git status, to see what files have an issue <br />2. git add <file>, fix then add those files <br />3. git commit ===Fixing rename errors in github===One problem that users can run into when trying to merge large number of files in github is the inability of renaming those files. The merge command on github have a limit to how much files can be renamed (not sure the "windows line error" questionexact limit, but I believe it is it not enough O^n limit). To increase the limit for large merge, users can re-set the upper limit with the help of the following command:<blockquote><pre>git config merge.renameLimit 999999</pre></blockquote>If you wish to simply re-set core.autocrlf to false and corethe default limit afterwards, then do this:<blockquote><pre>git config --unset merge.eol to lfrenameLimit</pre></blockquote> ===How do I get a Document (nsIDocument) from a Window (nsIDOMWindow)?=== Answer: Given aWindow, an nsIDOMWindow*
<pre>
git config nsCOMPtr<nsPIDOMWindow> win = do_QueryInterface(aWindow);nsCOMPtr<nsIDocument> doc;if (win) { doc = do_QueryInterface(win--unset core.autocrlf>GetExtantDocument());}git config --global --unset core.autocrlf// doc is now an nsIDocumentgit config --global core.autocrlf false</pre>
git config --unset core.eolgit config --global --unset core.eolgit config --global core.eol lf===How do I get from a Window (nsIDOMWindow) to a Widget (nsIWidget, nsBaseWidget, nsWindow, etc)?===
git lsAnswer: Given aWindow, see http://dxr.mozilla.org/mozilla/mozilla-files central/toolkit/xre/nsNativeAppSupportUnix.cpp.html#l201 <pre> nsCOMPtr<nsPIDOMWindow> domWindow(do_QueryInterface(aWindow)); if (!domWindow) return NULL;  nsCOMPtr<nsIBaseWindow> baseWindow = do_QueryInterface(domWindow-z | xargs >GetDocShell()); if (!baseWindow) return NULL;  nsCOMPtr<nsIWidget> widget; baseWindow->GetMainWidget(getter_AddRefs(widget)); // widget is now your widget</pre> ===How can I stack trace events in Firefox in Windows using Visual Studio?=== '''Answer 1:''' The answer is going to assume you know the basics of debugging on Visual Studio, like how to start debugging, step into, step out, step over, etc. If you haven't already follow the instructions on this [http://benoitgirard.wordpress.com/2011/05/27/using-visual-studio-2010-ide/ site]. You don't have to do the optional part. Make sure you build your debug version of Firefox before this. Once you've completed the tasks, find out where you want to put your break point, (use [http://mxr.mozilla.org/ mxr] or [http://dxr.mozilla.org/ dxr]), and then hit debug. When you rebuild Firefox, you won't need to do the steps all over again, your solution explorer will automatically update itself. See also https://cs.senecac.on.ca/~david.humphrey/writing/debugging-firefox.html, which is old, but likely still helpful. ===How do I programatically set the mouse cursor position?=== '''Answer:''' See how SynthesizeNativeMouseEvent does it on Windows: <pre>5941 nsresult5942 nsWindow::SynthesizeNativeMouseEvent(nsIntPoint aPoint,5943 PRUint32 aNativeMessage,5944 PRUint32 aModifierFlags)5945 {5946 RECT r;5947 ::GetWindowRect(mWnd, &r);5948 ::SetCursorPos(r.left + aPoint.x, r.top + aPoint.y);5949 5950 INPUT input;5951 memset(&input, 0 rm, sizeof(input));5952 5953 input.type = INPUT_MOUSE;git checkout 5954 input.mi.dwFlags = aNativeMessage;5955 ::SendInput(1, &input, sizeof(INPUT));5956 5957 return NS_OK;5958 }
</pre>
That should be enough to avoid checking out crlf ===How do I work with Preferences in Mozilla?=== '''Answer:''' See https://wiki.mozilla.org/Education/Learning/Preferences  ===Blur a window on a mochitest=== Instead of window.blur(), window.open() will blur the future and to checkout the repo again with lf line endings for all filesfocused window.
1
edit

Navigation menu