JUCE's Projucer has integrated GUI Editor.
How can I use the GUI Editor to create GUI during Audio Plugin project creation?
You have to:
Select NewComponent.cpp (assuming you created is using "Add new GUI Component")
Switch tabs (for example between Class and Subcomponents).
After these steps the "Add new component" functions become active.
I suspect that this is a bug in Projucer.
Related
I want to make an application in Visual C++ 2012 using MFC frameworks using Document/View structure; I want edit my view (that is the main window) with an editor, not handcoding, but Visual Studio seems that can edit in WYSIWYG mode just dialog boxes; I don't want to make a 'dialog based application', I want to make a Document/View application and edit my View with an editor WYSIWYG; Any solution?
You need to use CFormView as a base class when you creating your MFC application.
If you already have a project, then add a new form using the class wizard. Select CFormView as a base class.
When you open Resource View your new form will be listed in "Dialog" folder
In the last step of the wizard that creates a new document/view application, change the view base class from CView to CFormView. When you do that the CFormView can be edited just like a dialog.
MFC based apps have a WYSIWYG editor. Open the Resource Files folder of your dialog, SDI or MDI project and then open the .rc file. Menus and a toolbox should open up ready for editing.
I have been using Visual Studio IDE and I use Box Selection a lot.
Is the same possible for Eclipse IDE?
Since Eclipse 3.5 there is a button called Block selection mode in the main toolbar or you could use its hotkey as well:
Windows: Alt+Shift+A
Mac: Command+Option+A
See a blog entry about block selection for more details.
youtube walkthrough: How to enable block selection in eclipse and you'll be done in 2 minutes.
also explains how to setup custom hotkey, if Alt+Shft+A is already taken
I have a C/C++ algorithm that I want to create a GUI application for. I would prefer a .exe application that I can pass around to people. I would preferably want to create a dll of my c/c++ algorithm and then bundle it into the Windows GUI application which is basically just a wrapper around the main c/c++ application. How can I create this GUI in VC++ all with a couple of buttons, a text box and a file chooser/browser/opener?
Can someone throw some light on this problem?
Thanks,
Abhishek
There's a number of different options. First we have the microsoft-supported libraries:
MFC - The most heavy-weight library for the windows api.
ATL - A somewhat smaller, lightweight library.
Windows API - Use the Windows API directly.
Beyond that there's a number of third party GUI toolkits, notably:
GTK+
WxWidgets
If you want to make it as small as compact as possible and avoid external DLLs, you should use the Windows API directly or possibly ATL. This also gives you additional flexibility, but it's a bit more complicated. Take a look at for example theForger's tutorial. It's a bit old, but the api has remained more or less the same for the last ten years anyway.
Here's some additional pointers for using the API directly:
What is usually known as controls is called "windows" and are created using CreateWindowEx(). This function creates different things depending on the specified "window class", such as edit, button and static (described below). You create a regular window by registering a custom class.
You can use a function called GetOpenFileName() to invoke an open dialog.
The common text box is known as the edit control in the API.
Buttons are simply called button controls.
Labels are called static controls.
If it's enough for your purposes, you can also create a dialog window using CreateDialog(). This is possibly a bit easier, since dialogs can be designed using the resource editor, while you have to create all the controls in a regular window programmatically.
In Visual Studio:
File -> New Project
In the left panel choose "Visual C++" (or C# if you prefer) and in the right panel choose Windows Forms Application. Click Ok.
When your project is created, in the Toolbox panel you can find Button, Edit Box, OpenFileDialogs and SaveFileDialogs (which you need). If you can't find Toolbox panel, you can enable it in View->Toolbox menu.
Place the controls you need on the program window as you wish by simply dragging them over.
This is how I expected the toolbox to work:
Let's say I add a custom Tab to the Toolbox called "Ajaxtoolkit." To add controls to the new tab, I right mouse click and select "Choose Items" and browse to a file, Ajaxtoolkit.dll, that is of a particular version number.
I would expect that when I save and reopen the solution, that the Ajax Toolkit custom tab would still be in my Toolbox and that it would contain the same controls that were there last time, the controls that were in the dll that I referenced when the controls were added.
If I created a brand new web app, I (possibly) wouldn't expect to see the same Ajax Toolkit custom tab. However, I could perform the same steps as above and add a "Ajax Toolkit" tab and perhaps, this time, select a DIFFERENT VERSION of the tookit, and the state of the toolkit would be retained with each solution file.
Another possibility would be for the original Ajaxtoolkit to be retained when the 2nd web solution is created, and perhaps, if I wanted to mix versions of the toolkit across diffreent web sites in my solution, I should start naming my custom toolkit tabs with version specific names like "Ajaxtoolkit 4.0," etc.
...But instead, the Ajaxtoolkit tab disappears when I close VS2010 and reopen it.
Why? Is this desirable behavior or a bug?
You know VS2010 is a fully customizable IDE, may be these features conflicts your toolbox customization.
I'm looking for a Windows (pure DLGTEMPLATE output no .net resources!) dialog template editor (as a library or component) that can be used to modify or/and create new dialog templates for DialogBoxIndirect() function.
Use the Windows resource editor (part of Visual Studio) to create your dialog, then you can simply load the dialog resource to show the dialog.
You could also write some utility that reads the generated resource dialog and generate the DLGTEMPLATE data for it (I don't think it's that hard).