Posted: Fri Oct 17, 2003 9:35 pm
Ton's already fixed this nowdgebel wrote:1) I presume the "font with missing pixels" problem in the "background & settings" box is related to the object box problems already mentioned so I won't.
Would you please be able to provide a screenshot of this? Are you using AA fonts or not? (it should be the same either way though). When buttons are selected, the text should definitely not be black, but white like this:2) when buttons are selected, the dark grey background makes the black text VERY hard to read!!!!
What do you mean by 'View Modes'?3) Better visual communication of the "view modes".
That's a valid use (according to standards docs anyway) of ticks in menus, they can indicate both toggled selections and or radio-button-like choices. You can probably find something similar if you hunt around in some other apps - I know at least Photoshop does it. In Maya, and XSI they have the User/Front/Side/Top/Camera choices in a list like that although they don't use tick marks (treating the menu items like commands rather than selected choices). I thought it would be helpful and more logical to include the ticks to distinguish them as choices, from commands and to show the current state.some with checks, some without. If you select a checked item, shouldn't it UNcheck it? But it doesn't, and it doesn't make sense either - they are (n-state) radio buttons, not switches.
This is in the UI doc, and planned. Don't know if it will make it into 2.3 though.4) Maybe a new window type "Toolbar" where you can add or hide any of the menus you want. View port/type would be good there, and grouping would make radio buttons more obvious.
Yep, this functionality needs to be made more accessible and explorable. Thinking of a general 'window controls' menu-button in the window headers.5) For the truly new stuff, the collapsible buttons(?), awesome. How about a standard "options" VISIBLE button, rather than just Right Mouse
It was inevitable anywayI'd better stop now... Hope you don't mind all the detailed comments here!
Nope, it actually looks like this:broken wrote: Would you please be able to provide a screenshot of this? Are you using AA fonts or not? (it should be the same either way though). When buttons are selected, the text should definitely not be black, but white like this:
It is - wouldn't want it to be in the final build! What OS, graphics card, drivers? If anyone else is having the same problems can you please post the details, too? Also, if it's on Windows, can you try that more recent build on the front page and see if it's the same?Carnivore wrote:Just trying to be useful
Hmmm, I think something's really screwy with dependancies in mdk9.1 and the latest blender tree, and it needs to be fixed.UglyMike wrote:Segmentation fault in Mdk 9.1...
Ah well, looks ok on my Win2K at work but I couldn't really test it there...
I just hope we don't jump the gun too much and try to get it out of the door for the Conference. I'd prefer a buggy beta release to a buggy official Blender 2.3. Maybe wait some weeks/months for the coders to finish and for documentation writers, tutorial developers etc to catch up....
It's a known issueCarnivore wrote:Hey, I'm no expert, but would you consider this a bug: