×

Give a tip

7twenty

MX Master
  • Posts

    4,695
  • Joined

  • Last visited

  • Days Won

    79

 Content Type 

Profiles

Forums

Release Notes

Bug Tracker

Help page

Help page-CN

Release Note5

Rules and recruitment

Release Note6

Everything posted by 7twenty

  1. Maxthon.exe in Bin Maybe add a line stating "For Maxthon Portable you must set the correct install folder above" underneath the folder path field. Everything else looks good. Updated a few lines from the nsi file. Attached below. Mx_En_Updater.nsi
  2. I can only imagine the answer is yes. But it would also depend on the extension and how they work and interact with the page. Ones that run all the time will obviously be eating up CPU time compared to ones that only run when the user starts them. Ideally you'd only be running the extensions that you need, and not have 100 installed that rarely or ever get used.
  3. I made a few modifications to the Mx_En_Updater.ini file. Just minor changes to the wording. Also per this post, can you check the code for the MX4.9 flash update. For some reason when testing (using portable) it's not deleting/copying the pepflashplayer.dll file and also creating a webkit/npplugins folder which isn't required. Version detection seems to be off, or maybe just a portable thing?
  4. I've been on to them about creating a more user friendly info area for the extension API's with examples. Not on their plans though. A.S's guides are a good start. Explains well how to put together a few types of extensions. Unfortunately the only other option is in the SDK documentation especially for details on how to use the API's, which the info can be a little vague (at least for me). Probably OK if you have more knowledge with coding.
  5. I think he's talking about this one. Not sure if it includes what you want. Also might have to be updated to work with 4.9. Could be a good jumping point to create what you want if you/someone wants to.
  6. Trying to figure out some code to possibly port a chrome extension. The chrome extension includes this as part of the code: if (chrome.extension.onMessage !== undefined) { chrome.extension.onMessage.addListener( function (request) { if (request === 'refreshSettings') { chrome.extension.sendMessage(null, 'getSettings', chromeHandleMessage); } } Not sure how the chrome onMessage / addListener /sendMessage API's mirror those in Maxthon? I think it would related to mx.app.runtime.listen( type, func ) & mx.app.runtime.post( type [, obj] ) but not sure if that's right, or how to go about making that work as the above code does for Chrome? Any help would be appreciated.
  7. There isn't. The developer of that extension only makes it for the 4 big browsers. You could try contacting them and see if they can update it with support for Maxthon. Although, looking at the code the dev doesn't like coding for Firefox, so I don't know if he'd be willing to look into Maxthon given it's small install base. I'm having a look at the code to see if it's simple to port over. Will update with what I find.
  8. Access or login? Good news. But at least 3 people (the OP, A.S and myself) seem to be unable to login from the .com site. I also sent a feedback email and surprisingly received a reply. Have since replied and will wait to see what the outcome is.
  9. "Currently" meaning since the past week or two? As that's how long it seems to have been going on for? Why wasn't there a notification about this? How long till international users can access the english site to upload extensions? Why isn't the site based on the same backend and localised for different languages? Hopefully this "downtime" means something is happening to fix/update the extensions site. Surely needs some TLC!
  10. Is it? Just tried now and i'm getting wrong user/pass errors, even after resetting my password.
  11. ABP for firefox and chrome both have a built-in block by click option. Why the MX version doesn't is the question that needs to be asked. I found this bookmarklet a while ago which does a similar job. It can show you the element name but obviously not able to add directly to ABP, so a copy/paste is required to add to custom rules. Not perfect, but does help out and removes the need to go trawling through the code. You still need to add domain## to the element found in ABP. Because it's not originally created for ABP, some of the elements it finds might not work, so there's a bit of trial and error. I've also created an extension for it. Have uploaded to the extension site. I'll add some basic instructions to the extension page. SelectorGadget on Extension site.
  12. I haven't tried, just recall reading a thread about errors lately.
  13. I'd wait a little and try later/next day. There were some reports of things not working properly when updating extensions, it may be related to this as well. Hopefully will get sorted soon. I just tried logging in as well and i'm getting errors as well.
  14. MX4.9 needs the entire skin in the 0.dat file to function, unlike previous version where only the modified files are needed in the .mxskin file. So you'll need modify an MX4.9 skin with the files from the MX3 skin that you want, and then need to ensure that everything works, as it probably won't due to some changes. The simplest method is to extract the mx4 0.dat file then merge the mx3 skin files into that folder, only updating the files with the MX3 you require. But that won't work as there's quite a few differences in some files that need to be added as well. As i said above, unless you know HTML/CSS and have the time, it's not a case of just of adding a few files to make it work properly.
  15. If you know HTML/CSS then you'll quickly figure it out once you extract the file. If not, then unless you want to spend some time doing changes and seeing what happens, then it may not be worth the effort. Possibly best to wait till/if someone updates one for use with MX4.9. I did try to transfer the MX3 skin, but ran into issues with the avatar button top left. I gave up after that and instead just went to making the menu button go on the left instead of right.
  16. Tony pretty much explains it all very well. If it's crashing, you might have to do it the long way and adjust one bit at a time and hopefully you'll see what part is causing it to crash and then adjust as required.. I had the same issue when trying to mod the min/max/close buttons.
  17. Just checked. The sidebar always uses Ultra. But it also uses the user agent that is set in settings. Not sure if a user agent will help in this case, but even so, it will affect all other websites if it's changed. So probably not the best solution.
  18. Don't think that's an option. It will only work with the default renderer (Ultra). You can try changing your user agent and see if that has any effect on the sidebar
  19. it's up to the developer to update the extensions. Post on their forums about it: https://forums.lastpass.com/ or facebook: https://www.facebook.com/LastPass or twitter: https://twitter.com/LastPass
  20. NOTE: The information below is for Maxthon 4.4.x and earlier releases. For Maxthon 4.9.x and later releases see this post. Update to the most recent version of Flash from here: http://get.adobe.com/flash The page will show that it has detected Chrome. If not, check that the default user agent is in use. Click "Need Flash Player for a different computer?" Select your Operating System from the dropdown menu. Select "FP for Firefox - NPAPI" to install the correct version for Maxthon to use. Press the download button on the right and let the installer run. Close Maxthon. Open up an Explorer window (Win+E) and go to the folder you installed Maxthon to then navigate to the Core\Webkit\Npplugins folder. NOTE: Default install folders are:For 32bit OS - C:\Program Files\MaxthonFor 64bit OS- C:\Program Files (x86)\Maxthon In this folder there should be a file called NPSWF32_XX_X_X_XXX.dll (the X's are the flash version). Rename (eg. append .org to the filename) or delete this file only. Renaming is the recommended option. Restart Maxthon & goto http://www.adobe.com/software/flash/about/ The page should show the current version installed and the most recent version available, both of which should match. Maxthon is now using the current version of Flash. If everything was done correctly you should have something similar to the following image, and a Npplugins folder as below. Should the above not work, you can try copying the NPSWF32_XX_X_X_XXX.dll file from C:\Windows\Syswow64\Macromed\Flash (for 64bit) or C:\Windows\System32\Macromed\Flash (for 32bit) and paste it into Core\Webkit\Npplugins. If you have any issues with the above or other problems related to Adobe Flash with Maxthon please post in the following thread: Updated User Agent If the threads are locked please PM a Mod to reopen them. This ensures all the related information stays in the one place.
  21. NOTE: The information below is for Maxthon 4.9.x & 5.x releases. For Maxthon 4.4.x and earlier releases see this post. Update to the most recent version of Flash from here: http://get.adobe.com/flash The page will show that it has detected Chrome. If not, check that the default user agent is in use. Click "Do you have a different operating system or browser?" Select your Operating System from the dropdown menu. Select "FP for Opera and Chromium - PPAPI" to install the correct version for Maxthon to use. Press the download button on the right and let the installer run. Close Maxthon. Open an Explorer window (Win+E) and go to the folder you installed Maxthon to, then navigate to the \Core\Blink\plugins folder. NOTE: Default install folders are: For 32bit OS - C:\Program Files\Maxthon For 64bit OS - C:\Program Files (x86)\Maxthon In this folder there should be a file called pepflashplayer.dll. Rename (eg. append .org to the filename) or delete this file only. Renaming is the recommended option. Copy pepflashplayer32_XX_X_X_XXX.dll from the windows folder to the Maxthon \Core\Blink\plugins folder, and rename it to pepflashplayer.dll. The file is found in the following locations: For 64bit OS - C:\Windows\SysWOW64\Macromed\Flash For 32bit OS - C:\Windows\System32\Macromed\Flash Restart Maxthon & goto http://www.adobe.com/software/flash/about/ The page should show the current version installed and the most recent version available, both of which should match. Maxthon is now using the current version of Flash. If everything was done correctly you should have something similar to the following image, and a plugins folder as below. If you have any issues with the above or other problems related to Adobe Flash with Maxthon please post in the following thread: Updated User Agent If the threads are locked please PM a Mod to reopen them. This ensures all the related information stays in the one place.
  22. Available on the MX extension centre: http://extension.maxthon.com/detail/index.php?view_id=2940
  23. Thanks for that Amazingly the rest just seemed to fall into place once that was explained to me. Learnt a few things which is nice!