Category: Icetips Products

If you use the Enable Printer Selection extension on your Icetips Previewer to allow users to select a printer, then there is a bug that can cause problems. Fortunately it is very easy to fix it and it has been fixed in our sources for our next release.

The problem comes up if a user selects a page range to print from the PrinterDialog rather than selecting a page range within the previewer. This causes the FromPage and ToPage properties of the printer object to be set but there were two lines of code missing that reset those properties to default.

There are two places that you need to fix:

"Local Objects|Icetips Previewer|Print to Selected Printer|End of Routine"
and
"Local Objects|Icetips Previewer|Print current page to Selected Printer|End of Routine"

In both of those embeds, place the following code and the problem is fixed:

 Printer {PROPPRINT:FromPage} = -1
 Printer {PROPPRINT:ToPage} = -1

This has already been fixed in the next build which will be out later this week. It would be out today if it were not for a problem that we discovered before the weekend with Clarion 7. The cause of it has already been found and I'm currently working on a fix for it:)

Arnor Baldvinsson

I got an email this morning from a customer who was trying, without any success, to change the text of items in a Drop Combo control in PowerToolbar at runtime. The simplest way would be to simply use:

Toolbar1.SetItemText(MyItem,'My Text')

Unfortunately that only works for drop buttons, not Drop Combos. I figured it would be a simple task to add a method to do this but ran into a brick wall. The brick wall was the APIs used to construct Drop down Combo controls do not have any messages or methods to change the text for a given item! It seems to be set in stone once the item is created. So what can you do? The simple answer is to recreate the Drop Combo items! It is very fast and as far as I can tell it does not cause any flicker.

If you want to restore the text in the entry field, you need a single CSTRING variable to contain the text. Below is the code needed to reset the items in the Drop Combo:

Loc:Str = Toolbar1.GetText(ID1_DropCombo)
Toolbar1.DeleteItems(ID1_DropCombo)
Toolbar1.AddComboItem(ID1_DropCombo, 'NEW Drop combo item 1', )
Toolbar1.AddComboItem(ID1_DropCombo, 'NEW Drop combo item 2', )
Toolbar1.SetText(ID1_DropCombo,Loc:Str)

In this case Loc:Str is a CSTRING(100) variable that is a temporary buffer for the contents of the Drop Combo edit control. The Toolbar1.DeleteItems deletes ALL the items from the list and the next two Toolbar1.AddComboItem lines add two new items to the list. The Toolbar1.SetText resets the text in the edit control and you are back where you started except you now have updated items in your list.

Arnor Baldvinsson

A customer contacted me and sent me some screenshots of a menu themed with PowerToolbar that had several menu items missing from the last menu on the menubar. It was obvious that something was not working correctly so I asked him to export the appframe to TXA and email it to me. After duplicating this problem yesterday I spent couple of hours today investigating what was going on. Here is a screenshot of the menu:

Something was obviously wrong and my initial investigation wasn't promising. The API calls that get the information about each menu item simply weren't returning the text for the menu items! My suspicion was directed to a big menu with several levels of submenus as a possible culprit because it was the menu next before the trouble menu. So I cut it out of the source and lo and behold the Help menu worked again! I painstakingly copied the items and menus back into the menu until the Help menu failed and I had found the culprit.

One of the MENU statement had the HIDE attribute on it, and something about that set the menu item organization completely off and plunged the next menu into a deep hole! The fix was very simple, just remove the HIDE attribute from the MENU and add a one line of code into ThisWindow.Init to hide the menu.

 ?ReportsAddressBook2 {PROP:Hide} = TRUE

That's all there was to fix this problem. The menu now looks like it should:

This customer had also noticed another problem which was that the hotkey text on a menu item would disappear if the menu had a submenu and the submenu had been displayed. After some digging around I also found the culprit for that problem. When the submenu opened and closed the hotkeys for the items in the parent menu weren't reloaded so the width of each item was set to 0. This caused the hotkey text to be effectively drawn to the right of the menu. This is now fixed in build 2.0.118 which will be made available to the public after the weekend:)

Arnor Baldvinsson

One of my customers contacted me couple of days ago to ask if it was possible to sort items in a drop button, when the items are created at runtime. Since the items are stored in a queue I figured it would be fairly easy.

 Toolbar1.DeleteItems(ID1_Name)

 Toolbar1.AddDropItem(ID1_Name,'Arnor','ok_16.ico',1)
 Toolbar1.AddDropItem(ID1_Name,'Robert','ok_16.ico',2)
 Toolbar1.AddDropItem(ID1_Name,'Monica','ok_16.ico',3)
 Toolbar1.AddDropItem(ID1_Name,'Ana Maria','ok_16.ico',4)
 Toolbar1.AddDropItem(ID1_Name,'Ivan','ok_16.ico',5)

 Sort(Toolbar1.BandQ.ControlQ.pDropButton.ItemQ,|
      Toolbar1.BandQ.ControlQ.pDropButton.ItemQ.szTxt)
 !! Reset the ItemIDs after sorting the queue.
 Loop I# = 1 To Records(Toolbar1.BandQ.ControlQ.pDropButton.ItemQ)
   Get(Toolbar1.BandQ.ControlQ.pDropButton.ItemQ,I#)
   Toolbar1.BandQ.ControlQ.pDropButton.ItemQ.ItemID = I#
   Put(Toolbar1.BandQ.ControlQ.pDropButton.ItemQ)
 End
 Display()

Note that this will not work properly if you have separators in the drop items. If you want to do that, I would suggest to add the item text entries to a queue and sort them before you add them to the drop button. Something like this might work:

AddDropButtonItems         ROUTINE
 Data
Q   Queue
T     CString(256) !! Item text
SF    Byte         !! Separator Follows
    End
 Code
 Q.T = 'Arnor' ;     Q.SF = False; Add(Q)
 Q.T = 'Robert' ;    Q.SF = True;  Add(Q)
 Q.T = 'Monica' ;    Q.SF = False; Add(Q)
 Q.T = 'Ana Maria' ; Q.SF = False; Add(Q)
 Q.T = 'Ivan' ;      Q.SF = False; Add(Q)
 Sort(Q,Q.T)
 Toolbar1.DeleteItems(ID1_Name)
 Loop X# = 1 To Records(Q)
   Get(Q,X#)
   Toolbar1.AddDropItem(ID1_Name,Q.T,'ok_16.ico',1)
   If Q.SF = True !! Add Separator
     Toolbar1.AddDropItem(ID1_Name,'-','ok_16.ico',1)
   End
 End

 Display()

This should be able to handle sorted list with separators. I'm planning to add a method to sort the items alphabetically and I think I can make it handle the separators correctly too. The method I describe here is a bit more flexible as it gives you full control over how the items are arranged.

Arnor Baldvinsson

One of my customer asked how he could hide and unhide a band on a PowerToolbar on the application frame from a PowerToolbar button on his MDI window.

In order to do this you need to set up the MDI client template on the MDI window. PowerToolbar uses a global instance of the POToolbarGlobalClass to control the appframe toolbar from other threads. You can take a look at some of the methods in the online documentation.

The code you need to toggle the visibility of a band looks like this:

If AppToolbar.GetBandVisible(TB1_TestWindowBand) = True
    AppToolbar.SetBandVisible(TB1_TestWindowBand, False)
Else
    AppToolbar.SetBandVisible(TB1_TestWindowBand, True)
End

That is pretty much all there is to it. This is exactly the same code as you would use on the appframe itself.

Arnor Baldvinsson

You may find that you need to dynamically change the text in a header or item. This is a bit tricky in the currently public release, but is made much simpler in the next release.

In the current release, 2.0.111, you need to add a few lines of code to make this work. First of all you need to declare a group in your procedure data embed:

TskI GROUP(POB:TaskInfo)
     End

This declares a group that you then need modify.

 TskI = Outlookbar1.GetTaskInfo(OutlookBar1.Outlookpanel,0)
 TskI.Title = 'Changed Outlookbar Title'
 Outlookbar1.SetTaskInfo(OutlookBar1.Outlookpanel,|
                         0,|
                         TskI)

The first line loads the local group, TaskInfo, with the data from the header or item. The second line sets the title in the group and the third line updates the the header or item. Since this is rather awkward we decided to simplify this down to:

OutlookBar1.SetTitle(OutlookBar1.Outlookpanel,|
                     0,|
                     'Changed Outlookbar Title')

To download version 2.0.112, which includes the new SetTitle method, please go to Download Icetips Outlookbar 2.0.112

Arnor Baldvinsson

Sometimes it is necessary to update and refresh controls on the toolbar. In order to do so you need to know the control IDs. You can find those in the templates (see the "ID" field in these screenshots) or you can open the source for the procedure in the embeditor (right click on procedure and select "Source" from the popup menu) and locate declaration of the toolbar class (search for "POToolbarClass"). The IDs will be declared rigth above it and the control IDs start in a number range of 10,000.

Here is an example on how to update couple of entry fields and a checkbox button:

 loc:query     = SEA:Terms
 MinAsk        = SEA:MinAsk
 MaxAsk        = SEA:MaxAsk
 Toolbar30.SetText    (ID30_SearchEntry, loc:Query)
 Toolbar30.SetText    (ID30_MnPrice,     MinAsk)
 Toolbar30.SetText    (ID30_MxPrice,     MaxAsk)
 Toolbar30.SetChecked (ID30_Haspic,      Sea:HasImage)
 Toolbar30.Refresh(True)

Note that in order to make sure that everything is updated correctly you need to use Refresh(True) rather than just Refresh()

Arnor Baldvinsson

How can you execute an action in XP Taskpanel in code?

This is actually very simple to do, but may not be obvious. The following code was tested in the XPTaskpanelDemo_C6.app in the OpenWindow event handler in the ToolboxMenu procedure:

TaskPanel1.ExecuteAction(TaskPanel1.Demos, |
                         TaskPanel1.Demos:Colors, |
                         MouseLeft, 0)

This opens the Color Demo window when the taskpanel window opens.

Arnor Baldvinsson