MX Master
  • Content count

  • Joined

  • Last visited

Community Reputation

174 Excellent

About SnowLeopard

  • Rank
    Intermediate Mage
  • Birthday July 13

Profile Information

  • Gender Male
  • Location Maryland, USA
  1. The size of MX5 toolbar icons

    I have to apologize for misleading on the sizing. I forgot to include the units. The size is 20dipx20dip, dip not px. That doesn't invalidate anything you said, <<SL>> t invalidate
  2. The size of MX5 toolbar icons

    In my teesting, the siize is 20 x 20 on the toolbar (navbar). The icons on the tabs a rre 16 x 16. I haven''t checked the statusbar, but I recall then were also 15 x 16. I just checked; while the icon size is specified 20x20, the png size is 16x16. If they were converted to svg icons I wouldn't expect any bluring. <<SLl>>
    1. SnowLeopard


      Thanks, Magdalene.  I did find it here on the Releases page.



  3. MX5 PC Beta release

    Wheree's the portable button or link? I cannot use an exe on Ne nada, I found it on the Releases page. Why point to FB when it's right here on the Forum? <<SL>>
  4. Happy Easter and Revive the Feature You Love!

    I agree with all the suggestions but have some concern about suggesting the Chrome 59 core. The current release is 57 and 58 is in beta pending release pretty soon (I think). I just had a surprise when I happened to chect the default user agent string in Mx - it has Chrome 55, only 2 versions behind. If that is the actual core version, Maxthon is saying much closer to current than ever before. By the time of the next official release there should be a further core update to whatever is then current. <<SL>>
  5. Happy Easter and Revive the Feature You Love!

    I vote for these with Tony: 1 - New core 2 - full skin support 5 - a better ad blocker e.g., uBlock Origin which we voted for before And adding 6 - Update the skin SDK for MX5 -- this will help users and would-be skin makers learn how MX5 skins work.. 7 - Put main.solid into operation - expand Skin Center by adding ack the buttons that switched between main and main.solid; The primary difference was tabbar placement above or under all toolbars. That's what I have now. <<SL>>
  6. Maxthon 3/4 Skin SDK v1.1.17 (English Version)

    I have the same question - or equivalent. How do we make *.mxskin files that will override the contents of certain htm and css files packaged in UIMain.dat or UIHuge.dat? I know that MX5 will now loas *.mxskin files but just loading another background image is NOT a skin, not a real, full skin. I want an answer to my question and think it woukd be good to update the SDK with MX5 instructions. I have seen an mxskin file that loads a background image included in the file along with a congig.ini file like the one associated with the Skin Center files in MX5 and n UserData. That give clues to how a config.ini file is structured. But full skins for Mx3/4 have a xkin3.ini file. How is the MX5 equivalent file to be structured?? Plase give some help to skin makers so we can stop munging the default files in MX5. <<SL>>
  7. New Quick Access version 1.7

    Good call, The default skin QA is as it was. I am using a variation on wilser' Tabs Under the favbar" skin. I still see NO REASON why the addressbar text entry field should e fipping from addressbar to QA page and back. But i'my tweak only touch the tabbar and navbar and contents. <<SL>>
  8. New Quick Access version 1.7

    I can't confirm your observation. I never see the addressbar on the QA page since 1.7. I understood that was one of the 1.7 changes. <<SL>>
  9. Customizable Skins for MX5! - - 4000

    I'm with you Rick, I like the Mx4 Tas Over and Tabs Under buttons. I hope they're returned once they finish the work in UIHuge>main_solid. I've looked at it some and it doesn't seem complete yet. <<SL>>
  10. Customizable Skins for MX5! - - 4000

    I like the two ideas above, not the "Nitro" one so much.. I hope your count reaches threshold when some of your skins are ready. Welcome back. BTW, pleasecheck your IM for an off-topic request. <<SL>>
  11. Help w/ MX5 skin - where is Main Menu called?

    You can't now unless you make your own skin. The Skin Center has not been enabled. They have promised to bring skins back. In the meantime you might find some dark MX5 skins on the Chinese Forum. <<SL>>
  12. Help w/ MX5 skin - where is Main Menu called?

    Thanks. It worked, but left me puzzled why the same addition in UIMain/main/skin.css did not work and still left the question where Main Menu was called. So did some further exploration and found several things: 1. The skin.css files were commented out in the css_list.css files in both UIMain.dat and UIHuge.dat. So they didn'load and so sisn't work. They do work when loaded. 2. I found that I was overlooking the fact that the toolbar flow is horizontal, left to right. Cosequently I didn't look far enough in UIMain/navbar/buttons_right.htm and missed where Main Menu is called from UIHuge.dat. Thanks agin for kick-starting more exploration. <<SL>>
  13. I have a problem doing a skin in MX5, The goal is to reproduce the Under skin pattern fr om MX4. This pattern has the navbar at the top of the window and the tabbar second row. I can easily move the tabbar in the layout sequence and remove the reserved space on the tabbar for the winControls (min/resyore, max, & closr). However I cannot establish reserved space on the navbar for the winControls. I have tried: .navbar { margin-right: 120dip; } and .navbar { padding-right: 120dip; } but they do nothing to the navbar The problem seems to be the Main Menu. I am trying to find where it is called to load. It's reference in UIMaun.dat's index.htm is commented out. I can't find any other call to load it, but it dues load and soes so following the loadinf of the winControls in the body of the UI. Where is the call for Main Menu?? I want to make it move to the left of the winControls along with the navbar right end. <<SL>>
  14. Multiple rows of tabs addon

    Why don't you try the Translate fubction built into MX5. It works well for me (well as well as a computer translator can be wxpected to work.) <<SL>>