aMPed 3.3.2 Testing (1 Viewer)

[TLD]

Is this "aMPed-3.3.1.1701.mpe1" the right version?

 

[Dadeo]

Yes, 1701 is the latest revision. The release won't show as 3.3.2 until v3.3.2 is officially released - at least I am told that is how it should be done You may have noticed that MP is the same - the version numbers don't increase until a final stable release. (and it all confuses me immensely )

 

[TLD]

Very confusing. Looks like it fixed the latest media issues though. and it used my old config just fine.

 

[TLD]

Dadeo when you skin the World Weather plugin could you give each satellite view it's own page as when all 4 views are on the same page the images are quite small.

Thanks

 

[Dadeo]

World Wide Weather is now added to SVN (See Issue 443 ) It's already integrated into revaMPed and Vintage Basic Home layouts so displays your weather like Infoservice used to. The plugin is still in test mode, and there will likely be more changes, but at least we have our weather back for now and you can shiver at the cold without going outside

When I reinstalled aMPed it did not auto update the link for Weather on Basic Home which I changed in revaMPed and Vintage News>Weather sub menus. But I added World Weather to supported plugins so you can always add it yourself in the Editor if needed.

TLD - take a look at satellite images. I already did that! It's not quite perfect yet, but you have virtual views for each image and they display full screen. You can press the left arrow key to remove the menu and get a full view.

 

[2BitSculptor]

Thanks for the World Weather xml's!! very little problem getting ported to my mod.

There is one issue though, in Weather Maps, when viewing the alternate maps full screen, they revert back to the primary (satellite) map when the menu is hidden.

regards,

Chuck

 

[Dadeo]

There is one issue though, in Weather Maps, when viewing the alternate maps full screen, they revert back to the primary (satellite) map when the menu is hidden.

Yep, that is what I meant by 'not quite perfect yet' The problem is that the menu is controlled in the main window xml and images, etc. are imported into it. I had to add a dummy control so you could 'unfocus' the menu and see everything on 4x3 screens. It looks like I need to add a dummy control for each image type to allow you to navigate from/to the virtual view/map buttons but just haven't had time to do that yet. Unless you can think of a better/easier way?

I figure there will be more changes soon as well but I wanted to get the xmls committed so you could at least start using them.

Good to know they were easy to port to your mod Chuck!

 

[2BitSculptor]

I really like the way Maya looks .. I had already used the background image (with a color shift toward more blue) in my Rustic Blue mod. Now I'm trying to adjust the screens to include more of the Maya layout and graphics. It will be fun (I hope).

I did run into an issue with the style tag for the update notice icon. It was loading the background.png into that layer and covering everything preceding it. It took me 2 days to figure it out. Just WEIRD! I removed the style tag and filled in the other stuff to display it.

Did I say it will be fun?

Chuck

 

[2BitSculptor]

Ghosting menu items on Basic Home?

Is there a setting for "ghosting" a menu item button if is not installed/activated, and automatically skipped to next active item? If not, will the menu item have to be duplicated as an inactive button with the text color changed? That way all available/potential plugins can be presented in the sub-menu list, but seen at a glance that it is not active.

Chuck

 

[Dadeo]

Hi Chuck, do you mean in general, or on a specific aMPed screen? Since you mention sub menus, I assume you mean on Basic Home? If so revaMPed or Vintage layout? IIRC you use Vintage layout? If so, here's the answers:

• There is a disabled color setting for buttons (it is set to dull grey in aMPed). But it only works if the button is disabled not if the plugin is disabled. AFAIK you can only disable a button via code, not in the skin.
• To get different color text when plugin is enabled/disabled you have to create a separate (duplicate) control - but I cannot do that as I have no idea which plugin each user uses on which buttons. Currently the Editor does not support that, so if you do that, you will have to modify the skin files manually each time you change/move menu items.
• Although there is a kind of 'ghosting' control for buttons, it won't work on Basic Home sub menus because each item comprises several controls. Moreover, the Group Stacklayout control only allows you to close up space for missing buttons either vertically or horizontally, not both. I took a look at trying to use gridlayout controls, but it doesn't look like they will do everything I want either.
• Finally, I cannot set plugin is enabled/disabled visibility conditions in aMPed Basic Home layouts because, as I said above, I have no way to tell which button/plugin each user has moved/placed in which location or sub menu. It would require enhancements to the Editor.

It's a good idea Chuck, but not easily possible at present. I'll keep it in mind though, and if I can figure out a way to add it in future I will.