Bug 359

Summary: [Chameleon] button.php - does not handle less than 8 border images
Product: Chameleon Reporter: Fred Warnock <fwarnock@dmsolutions.ca>
Component: CoreAssignee: chameleon-dev <chameleon-dev@lists.maptools.org>
Status: CLOSED FIXED    
Severity: normal    
Priority: P2    
Version: 1.99   
Target Milestone: 1.99 beta 2   
Hardware: All   
OS: All   
Whiteboard:

Description From 2004-04-20 10:17:26 
Currently if you specify one border image, buttonizer expects 7 more and reports
errors if ther are none specified.

It should be able to handle any number of borders < 8 and draw nothing where
borders have not been defined.

an example is a tab, which does not have the bottom 3 borders.  those bottom 3
should be left undrawn because they have not been defined.
------- Comment #1 From 2004-04-21 11:33:27 ------- 
cannot reproduce ... it works for me with the latest cvs to specify only one
image (in my example I set just the left image).

do the errors appear in popups or the main app page ... and do they appear
through the error manager or in the page as php errors/warnings?
------- Comment #2 From 2004-04-21 16:06:24 ------- 
the errors appeared int the main page of the application, but only occur if you
do not provide the bottom right image.

the errors are as follows.

Notice: Undefined index: TEXTBUTTONBORDER_BOTTOMRIGHT_IMAGE in
C:\DMSG\msapps\chameleon1.1\chameleon\htdocs\widgets\Button.php on line 618

Warning:
imagecreatefrompng(C:\\DMSG\\msapps\\chameleon1.1\\chameleon_sample_fred\\htdocs//):
failed to open stream: Permission denied in
C:\DMSG\msapps\chameleon1.1\chameleon\htdocs\common\buttonizer\buttonizer.php on
line 660

Warning: imagesx(): supplied argument is not a valid Image resource in
C:\DMSG\msapps\chameleon1.1\chameleon\htdocs\common\buttonizer\buttonizer.php on
line 661

Warning: imagesy(): supplied argument is not a valid Image resource in
C:\DMSG\msapps\chameleon1.1\chameleon\htdocs\common\buttonizer\buttonizer.php on
line 662
------- Comment #3 From 2004-04-21 17:56:09 ------- 
fixed.  There was a copy/paste error that caused this.
------- Comment #4 From 2004-06-24 14:41:02 ------- 
verified using beta 2 2004-06-20 and closing