I've seen several limitations with the Designer Studio as well, and have reported these items to Codejock (including not being able to get rid of resource symbols).  Why don't we use this thread to communicate what we'd like to see in the designer.  The designer is a GREAT tool for building menus and toolbar, but there are some areas which, if improved, would make the tool even better.  Here are my ideas so far:

• More control over resource id's
• Delete unassigned id's
• User-defined values for each id instead of being forced to use the system-assigned value.  I would like to use number ranges for certain logical groups of resource id's, but it's impossible with system-defined values.
• Display the value for a resource id without having to create the 'resource.bas' file and lookup the generated value
• Sort resource id's when written to the 'resource.bas' file to find them easier
• Ability to load icons from ICO files (not just BMP files) with support for 32-bit alpha icons
• The 'Standard Toolbar' always shows up when I open a XCB file.  I don't have a toolbar called standard, and I always delete it.  But every time I re-open the file in the designer, the standard toolbar returns with all the same controls.
• Just a suggestion, but pressing the 'Insert' key on the keyboard to add a new Accelerator isn't very intuitive since the other aspects of the application (like Icons, Controls, and Toolbars) have toolbar buttons.  It took a while to figure this out when first using the tool.
• Field length limitation on 'New Icon' ID increased.  I believe the current length of the field is 32 characters.  The field length limitation on a 'New Control' ID is also 32 characters (although you can give it a longer ID by changing the value in the properties grid after the control is added).  Since icons with the same ID as a control are automatically associated, it's important to be able to give the icon the same ID as the control.  Since the icon is limited to 32 characters (with no work-around to give it a longer name), this isn't always possible.  There is a work-around to this problem as well, which is to simply create a new ID for the icon and then associate the control with that icon ID.  But this creates an extra resource ID that isn't entirely necessary.  If the field length could be increased, that would prevent the need for the work-around.
• Additional Theme Support for the Editor.  Unless I'm missing something, the editor always uses the Office XP theme for drawing toolbars and menus and they're built.  I prefer using the Office 2003 theme in my application.  While this isn't critical, it would be nice if the editor allowed you to build/preview your menus and toolbars in any of the supported themes.

I think that covers most of my comments, and I hope others will post their suggestions as well.  Like I said, the Designer Studio is great for quickly building your application's menu and toolbars.  Hopefully Codejock will incorporate some of our suggestions to make it even better.

I've actually sent all of these items to Codejock using their 'Feature Request' form, but I never got a response.  Actually, I've never gotten a response from anything sent via the 'Feature Request' or 'Bug Report' forms, so I stopped using those forms.  I did have a discussion with Oleg in the forums about support for ICO files, and I think they're going to consider it.  I don't know if 32-bit alpha icons are part of that plan.

Once we have some good feedback about other suggestions for the Designer Studio, maybe we can e-mail Codejock for their feedback (if we haven't already gotten it here).

Thanks boys. Nice suggestions.