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.
In Generic Inquiries, I've noticed that certain fields automatically have hyperlink functionality to open specific screens. I'm not sure what determines what screens these open (I'd imagine its based on whether its a key field for a maintenance table/DAC, etc.) - but I've also noticed that the manner in which it opens a screen is different for different fields / field types. Some open a popup with no menu, others open in the same screen space as the Generic Inquiry, and in doing so replace it in the browser.
My question is this: Is there a way to modify, in the GI setup, the manner in which it opens the screen so that it always opens as a replacement instead of a popup window?
If I remember correctly, with Acumatica ERP ver. 6.0 on the Generic Inquiries' Navigation tab there was added Window Mode drop-down to configure how the screen is opened from hyperlinks in a given GI:
I'm sure I am missing something straightforward and simple, but in xpages, using a tabbed panel, who do I get all the tabs to print when the users prints the page?
You can use a Dojo tab container (part of the extension library) instead of the standard tabbed panel. With the Dojo tab container the content of all tabs is loaded at once (in opposite to the standard tabbed panel, as Tim said), so you could do some CSS magic to make all tabs visible when printing.
Tim recommends building a separate XPage for printing, and I second that. Organize the content of the tabs in custom controls, create a new XPage for example with the suffix "_print" and include the custom controls in it without the tabbed panel. Then create a button, link or whatever in the first XPage which simple opens an XPage with the same name plus "_print" in a new window.
In the "_print" Xpage you can use a "window.print" after the page loads to open the print dialog automatically.
This technique has the advantage that you can style the printing exactly as needed. You can even control which content to include when printing by using the visible/rendered property and compute to render controls only when the current page name does not include "_print".
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
I would like to collect your ideas on the following:
SharePoint 2010 (and 2007) does have a preview button... while you are editing a publishing page you can switch to the "Page" tab and hit the Preview button:
Clicking this button does some magic to save your data, and opens a new window where the preview page is displayed. Nice, but could be better. What I would like is live update on editing of field controls from the edit page on the preview page.
My thoughts on this is are as follows:
Field types have an ID. For rendering the field values on your preview page, subclass from the standard FieldValue control, and render a span with the same ID around the field value html. So if we have the text ABC in the content editable div of a RichTextFiled X, render the field value as ABC in the display output (for example using EditModePanels for Display and Edit)
Add key-stroke event handler on all fields for the edit mode page (using for example jQuery), on key press copy contents from edit browser window to preview browser window
Transfer can be done using http://www.sfpeter.com/2008/03/13/communication-between-browser-windows-with-jquery-my-new-plugin/.
Does this sound doable? Would be great to work dual monitor, edit on one monitor, preview page in its real rendering on the other monitor. Especially if the edit mode differs from the display mode.
Looking forward to your input!
I will answer my own question. It is not as easy as its sounds. Fields can use things like reusable content and render patterns. These features render at server side, and change the output. This would require postbacks, which renders the whole thing useless. Lets stay with the already available preview button.