I am making a ribbon for my office. I have programmed all the macros already, except for the icons.
In the UI Editor, I have set everything to be done via a callback in VBA.
I have loaded all the icons using the MS Excel stock icons, however I have 9 icons that have to be added as they are not part of the excel standards.
I can't use different icons as the buttons in the ribbon paste the pictures that I need to display as the icons.
In the UI editor, I have set it up that all the buttons use "getimage=getimage" and have programmed a callback in VBA.
I don't seem to be able to change the 9 specific buttons to "image=pic1" and use the icons (pic1-pic9) I have loaded in the UI Editor.
When I try to do that, I get an error saying "the 'Image' attribute is not declared"
So now I am looking for a workaround in VBA.
Current callback code for a standard Icon:
Case "eButton03": RibbonImage = "ObjectPictureFill"
I need the code above to pull in a picture instead of using the standard icon.
let's say the picture is saved in C:\Pic\Pic1.png
Use this list: https://bert-toolkit.com/imagemso-list.html
You can also use or create custom images, add your picture "yourpic.png" via Excel's "Insert Icons" option in the Custom UI Editor.
Use the code
image="yourpic"
To use your picture as a custom icon.
I have created custom ribbon control in both the 2007 and 2010. i have added few features in 2010. i wanna use these new features in 2007 also. so for merging these i have used custom ui editor tool. and i have saved this as well. when i opened up this new to the 2007 all my new controls showed up correctly. but when i open it in the 2010, the controls showed correctly without the icon images. for example, control is "Picture" then nearby this control one small image will be there. this small icon images not showing up in the 2010 version. did i do anything wrong ? please anyone help me for showing it correctly !
Make sure you have added the icons as well to that version's xml. The pictures name must match the xml.
Click Insert and then Icons..., browse and select the pictures you want to use as button images.
You can have different sets of pictures for 2007/2010, but better to only use 2007 UI part if both versions are to be the same.
I am trying to create an InstallScript project using InstallShield 2013 Authoring Tool. So far I have just been using the default dialog boxes and skins. Now I need to now customize them to fit my needs, but I am finding the links in the help documentation to be lacking or broken. I was wondering if anyone knows how to create custom dialog skins or can point me in the right direction.
under "Project Assistant" tab, select "Installation Interview".
click on "Use custom images on dialogs" to specify your own images to replace "full screen image" and the "banner image" for the dialog.
large image size can be set to 499x312; banner can be set to 499x68 (if original theme used is 'Classic' or similar.)
till now, the dialog screen should look pretty good. But you will notice the installshield opening image (flash screen) is still using a default theme image. to solve that, create your own image (GIF format) to replace it, the size should be 157x312. use this image to replace the original 'setup.gif' under the folder:
C:\Program Files\InstallShield\2013\Support\Themes\Classic Theme.
(once again, all the image sizes and locations mentioned are based on the assumption that 'Classic theme of the dialog box is used)
You can download Skin Customization Kit from Flexera Software Product and License Center
Tinymce editor is used in the app. The rte toolbar is activated only if i click on the text area. I am able to focus on the Text Area using document.body.focus but still the rte toolbar doesn't show up.
WYSIWYG Editors has an example on how to automate TinyMCE Editor with watir-webdriver gem.
The Rte toolbar gets enabled only after a mouse click event. So I used left mouse click event to enable the RTE Toolbar.
b=WIN32OLE.new("AutoItX3.Control")
b.mouseclick "left",200,550
And it solved my issue.
I'm trying to understand InstallShield (2009)/InstallScript on the fly, because I'm modifying someone else's installation script.
One of the dialogs during the installation procedure previously had one textbox on it, asking for a SQL Server instance, assuming a certain database name. Now I've just completed an enhancement enabling you to choose any database name, not just the default, and I need to add a field to this dialog so the user can input the chosen DB name. Monkey see, monkey do, just make a new control and duplicate and adapt whatever functionality the form had for the first textbox - easy enough, right?
Umm... problem here. It seems that the "SdShowDlgEdit1" form is a generic thing that gets shipped with InstallShield, and is used all over, wherever you have a dialog that needs one textbox. Change that form, and it changes everywhere that it's called... so now I have a spurious 2nd textbox appearing all over my installation wherever there was a single text box before.
Oops. Undo changes, and change the reference to "SdShowDlgEdit2", which is - you guessed it - InstallShield's standard form for dialogs needing 2 textboxes. Now that would be great.... excepting that the previous developer got there before me and added a "browse" button to that form for a place where he needed the 2nd text box to contain a folder path. I don't want that "browse" button, and I can't delete it.
So I think, why don't I create a custom form of my own, and not get under anyone else's toes? So I clone the form, rename the new instance to "EnterDbDetails", delete the "Browse" button and make the form look just right.
Then I go back into the InstallScript to redirect to "EnterDbDetails" and discover that the EzDefineDialog function requires me to pass in the "Resource ID" of the form. Now what was it again... 12018... great... fill in all necessary details, compile, build, and give it a whirl. Looks lovely, all the right default values are filled into the two text boxes - but hey! Why is the browse button there? And why is the text on the labels not what I set?
Back to InstallScript, check the Resource ID - turns out that the original "SdShowDlgEdit2" also has a Resource ID of 12018. Well, that explains that nicely. Silly that InstallShield allows you to have two forms with the same ID, but whatever... So let's go back to my "EnterDbDetails" form and change the ID...
... but the Resource Identifier property is read-only! WTF?
So now I can't use any of the standard forms, and I can't use a custom form because it won't let me change the resource ID.
I am stumped. Can anyone please explain how you are supposed to do something like this, which really ought to be the simplest thing in the world?
Creating New Custom Dialogs in InstallScript and InstallScript MSI Projects
Quote from the site (2015 edition) :
To create a custom dialog, you need to perform the following general steps:
Use the New Dialog Wizard to add a new custom dialog to your project. For more information, see Using the New Dialog Wizard to Add a New Custom Dialog to an InstallScript or InstallScript MSI Project.
Add controls to the dialog. For more information, see Adding a Control to a Dialog in an InstallScript or InstallScript MSI Project.
Create a script function that loads the dialog into memory, displays it on the screen, handles the end user’s interaction with the dialog’s controls, and closes the dialog when the user is finished with it. For more information, see Using InstallScript to Implement Custom Dialogs.
To create a new dialog:
Open the Dialogs view. The Dialogs view is located in the User Interface section of the View List.
Right-click the All Dialogs explorer and then click New Dialog. The Dialog Wizard opens. Click Next to dismiss the Welcome panel.
In the Dialog Template panel, click Interior Wizard Panel, and select the Let me insert this dialog in a User Interface sequence check box.
In the User Interface panel, select Installation in the User Interface Sequence list. In the list of dialogs, select InstallWelcome. Based on these selections, InstallShield will insert your new dialog in sequence immediately following the InstallWelcome dialog.
In the Dialog Position and Condition panel, leave the default settings, and click Finish. Your new dialog appears in the Dialogs list.
Right-click the dialog and select Rename. Rename the dialog WelcomeBitmap.
Using the same technique, you can insert additional dialogs in your installation’s user interface.
In this step, you will modify the WelcomeBitmap dialog that you just created:
First, create a bitmap (using a program like Microsoft Paint) that measures 300 by 150.
Open the Dialogs view.
Expand the WelcomeBitmap dialog’s node. Click English (United States) to open the Dialog Editor.
Click the Dialog Bold Title text box at the top of the dialog. In the Text field, type Welcome Bitmap. This changes the dialog’s main title.
Click the Dialog Normal Description text box at the top of the dialog. In the Text field, type Displays my welcome bitmap. This changes the dialog’s description.
Click the Bitmap button on the Dialog Control toolbar and use the cursor to drag a box on the dialog. Set the Height to 150 and the Width to 300.
In the File field browse to the bitmap file that you created in step 1.
After rebuilding the project (by pressing F7) and running it (by pressing CTRL+F5), the Welcome Bitmap dialog will appear after the Install Welcome dialog.
You need to edit the ResourceID (to something unique) in the Dialog table which is found in the Direct Editor under Additional Tools section in the Installation Designer.
By custimizing standard InstallShield dialogs, like sdWelcome, sdFinish and sdFinishReboot you will be able to use the dialogs default script APIs with the performed customization's