Version 1.63 is now available for download.

  Updated 30 quests.

  Added auto sizing of height of minimap button window.
  Added quest option for "Color of watch areas when tracked". Set transparency to 0 to hide.
  Added quest option for "Color of watch areas on mouse over".
  Added "Auto watch changed quests". Checkbox added in quest options.
  Added sending of updated or best watched quest in status data.
  Added "*" to quest name in player map tooltip if quest is tracked.
  Added "Invite" to player map icon menu.
  Added quest info to tooltip for party map icons.
  Added display of received data for party member position if zone position not available.
  Added sub zone text to tooltip when moving mouse over map.
  Added "Minimap docks when map is maximized" and "Minimap hides when map is maximized" options.

  Improved guide visited vendor. Added type and location. Sorts by type. Can show on map and track using the icon.
  Added visited vendor max record count option. Default is 60 (was 12).
  Added "Options..." to guide popup menu.

  Added "Open Carbonite quest window using Alt-L" option.
  Added "Reload UI" to the reset options.

  Added "Disable global channel" and "Disable zone channel" to options.
  Added warning on login if not enough chat channels available.

  Fixed map not hiding on startup if minimap integration off.
  Fixed the 3 Caverns of Time instance icons being in same location.
  Fixed visited vendors data getting lost changing Carbonite versions.
  Fixed a few Blizzard minimap icons leaving holes in docking grid.
  Fixed minimap icons going under docking grid (DHUD, Trinity).
  Fixed quest completion update happening when quest fails.
  Fixed repeating error messages if not enough chat channels available.
 

faatal:

  Added visited vendor max record count option. Default is 60 (was 12).

What is the maximum?

I decided to put in 9999 as a test to see and it did accept it.  So I was curious.

 I don't have the code in front of me at the moment, but I think we ended up with 1000 as the max.

The number won't get clamped to the max until you talk to a vendor.
 

faatal:

 I don't have the code in front of me at the moment, but I think we ended up with 1000 as the max.

The number won't get clamped to the max until you talk to a vendor.
 

I talked to a vendor in TB and  now it does say 1000. Obviously it isn't a big issue but perhaps making it so noone can put in a number  higher than the maximum allowed  would help. It won't matter to me much, I will be lowering it now that my test is done.  But someone who puts in 1500 or something might not understand why it reverts  to 1000.

Thanks.

 I could make it a million, but I looked at the average memory use per vendor and settled on 60 for the default and a 1000 max, since I don't want someone using it for many months and saying all their memory is gone and FPS is crap because of Carbonite.

I changed the number validation code to clamp at 1000 max when you enter the number. So simple. Should of done that in the first place.

Thx