[MEL] image based UI problem

jeremy.ernst · February 26, 2009, 1:13pm

Hey all,

this is my first time doing an image-based UI using formlayout. I’m running into an error where my image buttons that lie on top of the background image dont show when first running the code. However, when I drag my mouse over where they should be, then they show up(but disappear again if I leave the UI window)

here is an image: (left is what it looks like when i first run the script, right after I drag my mouse over the button areas)

my background image does have the -isObscured tag as well. What could be causing this?

thanks!

jeremy.ernst · February 26, 2009, 11:00pm

edit:
nevermind, got it.
Stupid problem. the line declaring the background image was under the columnLayout instead of before it. oops

MoP · March 1, 2009, 3:03pm

omg Epic secretsss!!!

jeremy.ernst · March 1, 2009, 10:12pm

hehe. i got permission to post. no real secrets or giveaways Im afraid

MoP · March 2, 2009, 5:23am

i know that your games may be using characters with faces now!!

Rob_Galanakis · March 2, 2009, 5:30am

Not just faces, but strong faces with broad chins and square jaws! Are you working on a new IP?

rhexter · March 9, 2009, 1:58pm

Anyone had any legitimate draw issues with the Maya UI.

I seem to be running into a few problems with regards to dynamically created UI’s not drawing properly.

I get the same type of overlaid drawing problems as above however I know the script worked up untill the artists dropped aload more objects into a source directory that they want to be able to access through the UI in Maya.

Doe anyone know what the limitations are for numbers of elements within a UI, are there any?

Lard · March 10, 2009, 2:01am

I don’t know of any specific numbers of elements, but certainly if you create a lot ( a few hundred), you run into problems. I had a similar problem with our tools.

We have a frameLayout for each folder in an asset path. Then each asset has a icon and button within the layout. I altered the tool to only populate objects in the frame when the frame was expanded, the objects are then deleted when the frame is collapsed. This not only made the tool load a lot faster, but we could have a lot more objects as long as frames are collapsed, and a reasonable amount of subfolders are used.