What we at Icetips are doing
We at Icetips Alta LLC wish you all Merry Christmas and a Happy and prosperous New Year in 2010! We appreciate your business and support in 2009. Our office will be closed until December 28 and then from December 31. to January 4. We will still be checking our emails, but repsonse might be a bit slow over those two holiday weekends.
Arnor Baldvinsson and Susan Pichotta
While exploring the Clarion 7 IDE I accidentally came across a neat way to change the font size in the editor. Hold the Control key down and scroll your mouse wheel! It will increase or decrease the font size in a nice smooth action. For old timers like myself this is a very nice way to be able to zoom in to a section of code that I need to take a really close look at!
This works in both the file editor and the embed editor in Clarion 7. You can also set the font size manually by going to "Tools | Options" and then select the "Text Editor" node in the tree on the left.
Arnor Baldvinsson
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
Today I ran into a problem with a process on a SQL table. It was using a range limit and filters so it was only processing a subset of the data. However, the progress bar of course was stuck with the entire data set so it would go up to about 2% and be done. I have a procedure that I can pass some parameters to count the records in a table for a given filter so I knew exactly how many records the process was going to process. But I got stuck on how to reset the high limit for the progress bar. After some snooping around I found a property that I could set and everything worked like a charm.
!! First get the number of records.
!! SQ is a global equate: SQ Equate('<39>')
Loc:Recs = CountSQLRecords(Name(MyFile),|
'Parent_ID = ' & SQ & Loc:Parent_ID & SQ)
ThisProcess.RecordsToProcess = Loc:Recs
Put this code into priority 8550 or higher in the ThisWindow.Init method in the process procedure and the progress bar will now go smoothly from 0% to 100%
If someone has a method to call for this, please comment on this post. I could not find any method that worked, compiled and ran! Setting the RecordsToProcess property seems to have no bad effects.
Arnor Baldvinsson
Few days ago we received an email from a guy named "Tony" with the email address of tony@xgymzc.hk.cn. I have since received two emails from this same person, the last one with an email address of tony@skasia.hk.cn.
The first email went like this:
Dear Manager,
We are SK net service company ltd, the registration organization of trademark,internet brand and domain name in Asia.
On 15th,November.We have already received Juda Asia Industry Limited want to register (icetips ) internet brand and related domain names. After our department checked,you are the original owner of the brand,you have the first protection right. please let me know whether your company authorize JUDA to register them or regsiter them by yourself. If we can not receive your reply within a period,we will think that your company given up them and we will help Juda Asia Industry Limited to register them. Looking forward your response! Best Regards, Tony
SK Asia
Tel: 00852-3071 7712
Fax:00852-3071 7730
www.skasia.hk.cn
Today I received the third email and decided to look into this as this was sounding like a scam to me. After some snooping around I found this blog site with comments from over a hundred people about this scam. Basically they try to solicit people to register domain names with them, indicating that they have a client that is going to register your domain name with one of the East Asian domains, such as .cn, .tw, .hk etc. Currently you can simply go to Godaddy.com and register them, although the price can be quite high, for example the .tw domains are $39.99 a year.
I just thought I'd let my readers know about this so you know that this is a scam.
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
This past week both Sue and I have been suffering from the H1N1. Our daughter, Laila, got over it in two days and didn't really get sick with it, lucky her!
The problem isn't that it has been so bad - it hasn't! Neither of us has had fever, chills or bone aches, which we usually get with the flu, just nasty caugh og really bad fatigue. If there is one word that sums up H1N1 for us it has to be "TIRED"! As I'm writing this I don't really feel bad at all, still some caugh, but I have about as much energy as a disconnected spark plug - i.e. none at all! We are certainly grateful that it hasn't been worse, but it's that in-between state where you are not really sick but you can't really do much that isn't much fun.
So things are pretty much in very slow motion here these days and I apologize if emails have not been answered immediately! Hopefully we will be over this in a day or two:)
Arnor Baldvinsson
In my last blog I described my experience with the 1.5TB Seagate FreeAgent Desk external drive that I bought from Costco.
Instead I ordered a Coolmax CD-391T-U2 enclosure from TigerDirect and a 1.5TB Western Digtial drive. Wednesday I received the enclosures and the drive and immediately put the drive in. It was a bit tricky to put this together and the USB cable that came with it was only about 14-16" long. I plugged it in and the first thing I noticed was how loud the fan was. It was disturbingly loud!
First thing was to partition and format the drive and I knew that would take a while so I set it to do that over night. The morning after it was still formatting and I realized something was not right, so I stopped the formatting process and reconnected the drive to another USB port with another cable in case it was a cable/port problem.
8 hours later it was finally done with the format process so yesterday afternoon I started a backup process. I immediately realized that something was not right. It was barely getting 1MB pr. second transfer rate to the new drive. After messing around with it I realized that the enclosure seems to be having an issue with the USB to SATA conversion OR that it is actually designed for USB 1.1 not USB 2.0! So I decided to not mess with this and I am returning those to Tiger Direct.
After hours of checking things out I decided on my next enclosure to test out, a Vantec NexStar 3 NST-360SU-BL enclosure that supports both USB 2.0 and eSATA which supports up to 3Gbps (Gigabits per second) transfer rate compared to 480Mbps (Megabits per second) for USB 2.0 and only 12Mbps for USB 1.1! I should have those sometime next week and will report my experience with those. The Vantec does not have a fan so it should be quiet. It does come with both USB and eSATA cables (unfortunately the machine I'm using this with doesn't have an eSATA port, but more on that later) and get's 4.7 stars out of 5 available in 94 reviews on TigerDirect. The price is (currently) the same as the CoolMax, or US$29.99.
Arnor Baldvinsson
In September I bought a 1.5TB Seagate FreeAgent Desk external drive from costco.com. I had been looking for an external drive solution for backup purposes for a while and the FreeAgent drives looked good and we had previously bought two 500GB drives that performed without a single problem.
I plugged the drive in and everything looked good. I set up all my backup processing using the two backup software I use, InSync from Dillobits and Second Copy, both of which have served me well for years.
After I had set everything up and shared the drive, since part of the backup was from another computer, I rebooted my computer to make a clean start. That's when the problems started. During bootup I got an error message about a drive being problematic, don't remember exactly what it was, and the disc diagnostic program insisted to run on my C: drive. Everything checked out and no problems were reported.
I set all my backup processes to start and did some direct copying as well and after about 12 hours all the data was in place. For the next few days everything worked fine, but then one day I got an error message from windows telling me that there was a write error and it couldn't write the Q:\$MT file or something like that, Q:\ being the drive letter of the FreeAgent drive. This persisted for a few days and then everything seemed to be working ok again and for the next 5 weeks or so no problems at all, so I decided this was something for the history books.
About 3 weeks ago I decided to buy another drive of the same type so I can rotate the drives for an off site backup, which I use the removable drives for. I have been very busy lately and I delayed putting up the drive until last weekend.
This new drive started out with write errors from the start. I re-partitioned and re-formatted the drive twice to see if I could get it to work, but no help. I ended up returning it to Costco for a full refund.
So I did some research online to try to find out what the heck is going on with those drives. Well, you don't have to look very long to find people who have had a lot of problems with the 1.5TB FreeAgent drives! One of the websites I found was this one. It claims that the problems are caused by overheating, which I can relate to since there is no ventilation for the enclosure, it is completely closed off! I could also feel it getting pretty hot and someone that posted about this had measured the drive temperature getting up to 250
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