var my_style_group = new StyleGroup();my_style_group.Label = new Style();// ...StyleSettings.addStyle("CoolTheme", my_style_group);// ...StyleSettings.removeStyle("CoolTheme");
How about a 64-bit build?
Quote from: N E O on August 20, 2013, 03:23:31 pmHow about a 64-bit build? I honestly don't see what 64-bit gains us at this stage of development. Nothing in it uses ludicrous amounts of memory (seriously, if I start seeing 2+ GB maps I'm running for the hills) and it's an IDE so there are no CPU-intensive tasks it does that would benefit from the extra registers/expanded instruction set. A 64-bit engine makes sense, but it just seems like overkill for an editor. Maybe that's just me, though.
In this day there is still little reason to go 64 bit, it was only pushed to the consumer market as a business strategy since "32 bits" was basically sounding too old. But I mean, I can make such a build, even if it doesn't make a lot of sense it's really just a button click away.
Hm, not sure I like the list backgrounds being muted like that, especially since almost every other app uses white for the back of lists (a dull background is usually an instinctive visual cue that the control is disabled).
We can make custom themes later that use a different back color for the lists, but the built-in ones should stick to white, I think. As for the secondary style, it seems like a good idea, but I'm not entirely sure I understand its purpose.
Oh, and the Apply button is in an awkward position. Almost every Windows app I've ever used puts the buttons in this order: OK, Cancel, Apply.
And regarding VS2012: They added more color to the icons in VS2013 (folders are back to being manilla, and the toolbar icons are more colorful and stand out more), and the VS2010-style "Blue" theme seems to be the default now. I guess they learned from their mistake.