7twenty

Vice Admin
  • Content count

    4,672
  • Joined

  • Last visited

Community Reputation

1,228 Excellent

About 7twenty

  • Rank
    Senior Member

Profile Information

  • Gender Not Telling
  • Location : Australia

Recent Profile Visitors

29,278 profile views
  1. I'm pretty sure this shouldn't be happening, or at least not available for anyone to find. Plain text MX_LOG_XX.log files in windows' temp folder. Sample attached with URLs obfuscated. MX_LOG_11.log
  2. Parallel Beta Versions?

    That's always how it is and has been for ages. You release version 1.0, then work on 1.1. During that time there may be work going on for features in 1.2 or later, which may get released as a beta. It's not hard to decipher. That's not a bad idea to have an extra line stating it's a beta, BUT it already says it's a beta in bright red, and in the filename - I'm not sure how many extra times BETA has to be added in the description. Whether it's 5.2.x beta or 5.3.x beta makes no difference. If you don't want to get caught up with the issues a beta version could lead to, then you don't update/download to ANY beta version. There is except it's for pre-public release. Those that are enrolled in it can access it, but it requires that the MX guys actually utilise it properly. Unfortunately they have their own agenda which makes it effectively useless.
  3. netflix not working again

    True, but that's where you need to make the decision - do you want a browser that does the basics well with some foibles around the extra features? Or one that has issues with popular websites, but having better extra features. Only the user and their usage scenario can make that call. Vivaldi still has a lot of things that bug me, (eg. no new tab from enter on address bar, no media controls on popup videos, having to use an extension button to popout videos instead of the floatbar, super drag/drop isn't quite as good), BUT it's always up to date, UI that is as customisable as MX if not more, more extensions, chrome://flags is available, and more that i can't think of right now. About ~21mb, and it's returned to the system after the video is popped out. - RE: screen capture: it is basic, but i find myself going into a dedicated image editor 90% of the time even using MXsnap. One thing that it does do well is being able to automatically select windows/sections of apps, which i would miss. But i still have MX running till i import passwords etc. so still use Snap on occasion. Notes: haven't used it since SkyNote. Most things i put into sticky notes or OneNote these days. I feel that Vivaldi (~v2.3) has finally become what MX wanted to be. Sure MX does a few things better, but most unique MX features are in other browsers now and they do it almost as good, or do other things better to make the benefit a net loss, or even at best.
  4. netflix not working again

    Netflix/Facebook/Twitter/Spotify/youtube etc should work first go everytime. This is the internet for a majority of users. You stuff up that experience and you're already giving the user a reason to jump to another browser. Vivaldi.
  5. Folder length very short maxnote

    Edge and Vivaldi for 2. Agree. It's either an arbitrarily defined limit or an oversight. There's not really any reason why it should be limited to that.
  6. Works fine here, and on .400 *shrugs* Possibly a network/browser combination issue?
  7. did you check to see if it is enabled in settings? if so, disable/enable and try again.
  8. Darling, there is someone that is wrong in this thread, and it isn't me. If working normally means keeping focus, then that would mean either 1/ there is something wrong with your version, 2/ you've done something with a 3rd party program to add that feature. Normal functionality is that it is only in focus when instigated via a command (menu option/keyboard shortcut/download prompt). There's plenty of answers here, and the outcome is - it's working as intended. Yes, and we understand there is no problem. It seems we agree on what your alleged issue is, but don't agree that it's an actual issue because it's NEVER functioned as you describe. So either there's a communication breakdown here and we're talking about something else, or as noted above, you've done something to add that feature (possibly without knowing?!) I normally say repeating something doesn't make it true, but in this case i'll let that slide because what i'm saying is a bona fide verifiable fact: - MX downloader NEVER, EVER stayed in focus while downloads were running. EVER.
  9. Not sure what this guy is on about. MX downloader has NEVER stayed on top. If you click the MX main window it always takes focus. The Downloader prompt will take focus once you click on a downloadable link, and subsequently the download manager. While the file is downloading, the manager doesn't stay in focus unless you explicitly click on the taskbar icon, use Ctrl-J, or the Downloads option from the main menu. There's no indication from the posts or images to show that the taskbar icon is not being displayed.
  10. I don't believe there's any confusion, i think they have a system in place, just that maybe things get mixed up when they update the listings. Normally the last number will show if it's a beta/final version. RC's are normally tagged with RC. <1000 is beta, 1000 or 2000 is final. If there is going to be a .2000 release then there may be beta versions between .1000 > .2000 (eg. 5.2.5.1200). Bugfix releases generally get re-released under the same number (which they shouldn't but whatyougonnado?). 5.2.7.x seems to be an odd one. In release notes, it's marked as beta, but tagged as RC in the filename. Then the final shortly after that. I think someone got confused with this one. Ideally they'd be a little more defined. <800 beta, 900 RC, 1000/2000 final. Then any bugfixes between those get a small bump, so 921 is a RC with some fixes since 900, then released as 1000. You shouldn't look at when they're released, but look at the version numbers. If you're testing beta versions then stick with them. If not then stick with final versions. Definitely don't jump between them. If that doesn't make sense then probably best to just leave things as they are.
  11. 5.3.8.300 gone?

    Thanks for proving me right. Originally I was going to post a screenshot of the log, but figured i'd be accused of editing it. But now apparently the logs don't "log". Well there you go. Maybe someone should let IPS know that their forum software (which is built on a database of logged entries) doesn't work properly.
  12. 5.3.8.300 gone?

    Logs say nothing happened. The only threads deleted or hidden were NOT related to any of the x.x.x.300 threads. Think what you want, but nothing happened.
  13. 5.3.8.300 gone?

    Was never gone. I just used my eyes, found it in the unpinned threads and pinned it. Was still in the release notes as well. I've always been quite open about my thoughts of the browser and their processes, but seriously, the amount of conspiracy theories and constant digs on their "testing" is getting beyond ridiculous. 5 random users "testing" a release 1 day before official release a "test team" it does not make. But yes, whatever internal testing they did failed big time on this release - but it is a beta(!) and a new core!
  14. Maxthon vs. Fullscreen apps

    Yep it does make you cry doesn't it... Seems it's not fixed, the issue is back although doesn't seem to be as repeatable as it used to be. Might have been a one off or something. Given the number of posts of issues of the most recent beta, it seems the core upgrade has caused a lot of issues. Being a user who used to use MX everyday as my only browser, i've now gone to Vivaldi, using MX for various things like logins that i haven't moved over yet. But this bug could well be the one that pushes me right off the edge. It's just too annoying having to close the browser just to make something else work properly, even though that program isn't even at fault.
  15. Maxthon vs. Fullscreen apps

    Seems to be fixed in 5.3.8.300