[Resolved] [6.0.0.13] Testers required.

NOTE: All issues raised in this thread were related to a particular series of builds where the control painting methodology was being redesigned.
These issues have now been RESOLVED.
kwb.
///------------------------------------------------------------------------------------------

I'd like as many people as possible to try to run this code.

It's a simple Tab Control with 3 Pages

When the code is run ;

Command : DOIT

The user should see Page 1
.. a TextButton, A textBox and a Graphics Button.
Ditto for Page 2
Ditto for Page 3.

If you can't see the controls, just move the mouse pointer over the tab page.
If you can't see the TextBox properly, Click the button.
if you cant see the graphicButton Select (Pick) on the Tab Page till you find it.

This is not a trick program.
I'm getting different results on different computers ...
Please post back with your results
and AcaD Version, OpenDCL Version, Machine details(if possible).

Best Regards and Thanks
kerry



;; Test Code
;; 20091111 kdub@home

;|<>|;


(defun c:doit () (c:Test60012b))

;;----------------------------------------------------------------
(defun c:Test60012b (/ DialogReturn)
 (command "_OPENDCL")
 (dcl_Project_Load "kdub60012b.odcl" T)
 ;; Show the main form
 (setq DialogReturn (dcl_Form_Show kdub60012b_Main))
 ;;------
 (princ)
)
;|<>|;

;|<>|;


;;-----------
;;-----------
(princ " << Enter DOIT or 'Test60012b' command to run >> \n")

Fast check in one of my workplace mashine in two ver. of ACAD.
At home, i will check on my notebook, and workstation, with more runtime versions.

So now.
-----
AMD Athlon 64 x2 5000+ 2.60 GHZ
2 GB of RAM
on Gygabyte Tech M720-US3
Windows XP Pro sp.3 (5.1, Build 2600)
NVIDIA GeForce 8600 GT, with old driver=> 6.14.11.6923
DirectX 9.0c (4.09.0000.0904)
Visual Style (Theme) => WindowsXp Default(blue)
-----

OpenDCL Runtime [5.1.2.3]

:ACAD 2004
----------------
Command: acadver
  ACADVER = "16.0s (LMS Tech)" (read only)
Command: _vernum
  _VERNUM = "V.0.86" (read only)

:ACAD 2010
----------------
Command: acadver
  ACADVER = "18.0s (LMS Tech)" (read only)
Command: _vernum
  _VERNUM = "D.215.0.0 (UNICODE)" (read only)


No problems. Everything looks fine.

Hi Kerry,

easy answer:

Every Machine: Visual Styles enabled, OpenDCL 6.0.0.12 DEU, ODCL-project read from network drive via additional supportpath
All (but one) AutoCAD releases DEU

Machine 1 (Tower): WinXP x86 DEU, AMD XP 3200+, 2GB RAM, ATI RADEON 7500
Tested in: AutoCAD 2004, AutoCAD 2008, Map 2008, Civil 3D 2009 (all x86)
Result: All controls are shown properly, no flickering, nothing bad to tell.

Machine 2 (Tower): Win Vista x64 DEU, Intel Xeon E5504, 12 GB RAM, NVIDIA Quadro FX 580
Tested in: AutoCAD 2010 x64, AutoCAD R18.1 x64 Beta 1 ENU
Result: All controls are shown properly, no flickering, nothing bad to tell.

Machine 3 (Notebook): Win 7 x64 DEU, Intel Core2Duo T7300, 4GB RAM, NVIDIA GeForce 8600M GT
Tested in AutoCAD Map 2010 x64
Result: All controls are shown properly, no flickering, nothing bad to tell.

On Windows 7 x64 I suggest to call the form again and again and again: I have the feeling that my forms are getting slowlier and slowlier each time they have to be shown. I'm still testing our product on Win 7 x64, too.

Fred

author=Slavko.Ivanovic link=topic=1008.msg5137#msg5137 date=1257950479 wrote:
Fast check in one of my workplace mashine in two ver. of ACAD.
At home, i will check on my notebook, and workstation, with more runtime versions.

So now.
-----
AMD Athlon 64 x2 5000+ 2.60 GHZ
2 GB of RAM
on Gygabyte Tech M720-US3
Windows XP Pro sp.3 (5.1, Build 2600)
NVIDIA GeForce 8600 GT, with old driver=> 6.14.11.6923
DirectX 9.0c (4.09.0000.0904)
Visual Style (Theme) => WindowsXp Default(blue)
-----

OpenDCL Runtime [5.1.2.3]

:ACAD 2004
----------------
Command: acadver
  ACADVER = "16.0s (LMS Tech)" (read only)
Command: _vernum
  _VERNUM = "V.0.86" (read only)

:ACAD 2010
----------------
Command: acadver
  ACADVER = "18.0s (LMS Tech)" (read only)
Command: _vernum
  _VERNUM = "D.215.0.0 (UNICODE)" (read only)


No problems. Everything looks fine.

NEWS!
Test no.2.
Same machine, same ACADs,
but i have just installed:

OpenDCL Runtime [6.0.0.12]

and...
In both ver of AutoCAD same (bad) behavior:

--------
Always on Start or Tab change :
I only can see Text Box , but looks like disabled and i can not see text inside.
--------

after showing...

scenario:
1. If I first click in Text Box I see this control correct.
  When I click in Text Box Graphic Button get visible, but Text Button is still not visible.

scenario:
2. If I first move mouse pointer over area where Text Button should be, then (on mouse over) Text Button get visible.
  Text Button get visible, but still can't see Graphic Button, and Text Box still look's like disabled.

scenario:
3. If I first click in area where Graphic Button should be, then (on mouse click) Graphic Button get visible.
    But Text Button is still not visible, and Text Box still look's like disabled.

--------------------

So after this i tested some of my forms with Tab controls, and they are "acting strange".
Example in one form, when i change Tab, some controls in that Tab have delay 1-3 sec before get visible.

So, on absolutely same configuration:
OpenDCL Runtime [5.1.2.3] - NO PROBLEMS OF ANY KIND
OpenDCL Runtime [6.0.0.12] - FORM and CONTROL SHOW PROBLEMS

Hi,

AMD Athlon XP 3200+, 1x2,2 GHz
2 GB of RAM
on MSI KT6 Delta-FISR (MS-6590 v2.0)
Windows XP DEU Version 5.1.2600 Service Pack 3 Build 2600
ATI Radeon 7500 DDR using Windows Driver (uses no CCC!)
DirectX 9.0 (installed by AutoCAD, no idea how to find the subversion)
Visual Style (Theme)
tried with WindowsXp Default(blue)
tried with WindowsXp Silver
tried with WindowsXp Olive
tried with Windows Classic
-----

OpenDCL Runtime [6.0.0.12]

:ACAD 2004
----------------
Command: acadver
  ACADVER = "16.0s (LMS Tech)" (read only)
Command: _vernum
  _VERNUM = "V.0.86" (read only)

:ACAD 2008
----------------
Befehl: acadver
ACADVER = "17.1s (LMS Tech)" (schreibgeschützt)
Befehl: _vernum
_VERNUM = "B.51.0 (UNICODE)" (schreibgeschützt)

I've tried several combinations of Visual Styles, Hardware accelerations and manual tuning of _3dconfig.
In every case I can see no problems.

Fred

DirectX 9.0 (installed by AutoCAD, no idea how to find the subversion)

[WINKey+R], dxdiag

Start -> Run -> dxdiag -> OK

Test no.3.

shortly:
My notebook IBM  THINKPAD T43.
XP Pro. SP3

:Acad 2004
:Acad 2009
:Acad 2010

all ENU.

OpenDCL Runtime [5.1.2.3] -> ALL OK !
OpenDCL Runtime [6.0.0.12] -> PROBLEMS SAME LIKE IN MY Test no.2.

author=Slavko.Ivanovic link=topic=1008.msg5141#msg5141 date=1258029278 wrote:
Start -> Run -> dxdiag -> OK

Thanks, now I know that I have 4.09.0000.0904, too.
I see, the only difference between our workstations must be the language  ;) ?

Fred

author=Slavko.Ivanovic link=topic=1008.msg5139#msg5139 date=1258023857 wrote:

NEWS!
Test no.2.
Same machine, same ACADs,
but i have just installed:

OpenDCL Runtime [6.0.0.12]

and...
In both ver of AutoCAD same (bad) behavior:

--------
Always on Start or Tab change :
I only can see Text Box , but looks like disabled and i can not see text inside.
--------

after showing...

scenario:
1. If I first click in Text Box I see this control correct.
   When I click in Text Box Graphic Button get visible, but Text Button is still not visible.

scenario:
2. If I first move mouse pointer over area where Text Button should be, then (on mouse over) Text Button get visible.
   Text Button get visible, but still can't see Graphic Button, and Text Box still look's like disabled.

scenario:
3. If I first click in area where Graphic Button should be, then (on mouse click) Graphic Button get visible.
    But Text Button is still not visible, and Text Box still look's like disabled.

--------------------

So after this i tested some of my forms with Tab controls, and they are "acting strange".
Example in one form, when i change Tab, some controls in that Tab have delay 1-3 sec before get visible.

So, on absolutely same configuration:
OpenDCL Runtime [5.1.2.3] - NO PROBLEMS OF ANY KIND
OpenDCL Runtime [6.0.0.12] - FORM and CONTROL SHOW PROBLEMS

THANK YOU !!!!

I have the same issue on several machines.

////...

Just for Info : are any of the tests using a dual monitor setup ??

Yes, I have. I wanted to tell it in my last post but I deleted it because I thought it would not be important. I have no display problems on all three machines. My XP tower with the Radeon 7500 graphics card uses 2 Samsung 2343BW with a resolution of 2048 x 1152 for each.

Fred

There is definitely a problem, but I'm not sure what the solution is.  For Alpha 13, I'll try making a few small changes to see if anything changes.

Here's another one which is causing me trouble.

I have Slides that the user selects a location on. Dependant on the location selected, some textBox and Buttons may be made visible.

This is a sample.

Note that the draw method in both the slide and PictureBox seems to not work at initialisation.
.. (but perhaps I'm doing something wrong 'cause I bashed this together.


If you comment the code

  (dcl_slideview_fillimage test_1113a_main_slideview1 
                          (list (list x y 10 20 3)) 
  ) 
  (dcl_slideview_endimage test_1113a_main_slideview1)

in c:test_1113a_main_slideview1_onmousedown (so that the fillImage Method is not used) the SetVisible works as expected.



(vl-load-com)
(command "OPENDCL")

;; Test Code  
;; 20091113 kdub@work  

;|<>|;


;;;---------------------------------------------------------------------------
;;; (findfile "Test_1113A.ODCL")
;;;---------------------------------------------------------------------------
;;;
(defun c:test_1113a (/ dialogreturn)
 (dcl_project_load "Test_1113A.ODCL" t)
 ;; Show the main form  
 (setq dialogreturn (dcl_form_show test_1113a_main))
 ;;------  
 (princ)
)
;;;---------------------------------------------------------------------------
;;;
;|<>|;

;;;---------------------------------------------------------------------------
;;;
;|<>|;

(defun c:test_1113a_main_oninitialize (/)
 (dcl_control_setvisible test_1113a_main_textbutton1 nil)
 (dcl_control_setvisible test_1113a_main_textbox1 nil)
 (dcl_control_setvisible test_1113a_main_textbutton2 nil)
 (dcl_control_setvisible test_1113a_main_textbox2 nil)
 ;;
 (dcl_control_setbackcolor test_1113a_main_picturebox1 8)
 (dcl_picturebox_drawcircle
   test_1113a_main_picturebox1
   (list (list 10 10 30 30 2) (list 30 30 20 40 6))
 )
 (dcl_PictureBox_StoreImage test_1113A_Main_PictureBox1)
 (dcl_slideview_fillimage test_1113a_main_slideview1
                          (list (list 30 30 25 25 3))
 )
 (dcl_slideview_endimage test_1113a_main_slideview1)
)
;;;-------------------------------------------
;;;
(defun c:test_1113a_main_picturebox1_onmousedown (button flags x y /)
 (dcl_control_setvisible test_1113a_main_textbutton1 t)
 (dcl_control_setvisible test_1113a_main_textbox1 t)
 ;;
 (dcl_picturebox_drawcircle
   test_1113a_main_picturebox1
   (list (list (- x 15) (- y 15)  30 30 3) )
 )
 (dcl_PictureBox_StoreImage test_1113A_Main_PictureBox1)
)
;;;-------------------------------------------
;;;
(defun c:test_1113a_main_slideview1_onmousedown (button flags x y /)
 (dcl_control_setvisible test_1113a_main_textbutton2 t)
 (dcl_control_setvisible test_1113a_main_textbox2 t)
 (setq xx x)
 (setq yy y)
 (dcl_slideview_fillimage test_1113a_main_slideview1
                          (list (list x y 10 20 3))
 )
 (dcl_slideview_endimage test_1113a_main_slideview1)
)
;;;---------------------------------------------------------------------------
;;;

(prompt "\n TEST_1113A to run.")
(princ)

It is not possible to draw on a picturebox in OnInitialize because the picture box is not yet visible at that point. This is the case because the draw methods draw directly onto the display. The same thing would happen with slideimage. For the picture box, you can do the drawing during OnPaint.

Thanks Owen,
I don't usually draw on initialise, just tried for this sample. ... I'll keep that in mind for future.

added:
I would like to draw in the slide to indicate the location selected though
... this is why ... see the green marker, it indicates the reference point selected


Just for info, the 'Insert Options' and 'Draw 2D' 'Draw 3D' buttons don't display untill the workpoint is selected.

author=Kerry Brown link=topic=1008.msg5136#msg5136 date=1257934500 wrote:

I'd like as many people as possible to try to run this code.

It's a simple Tab Control with 3 Pages

Tested on ODCL - 6.0.0.12, AutoCAD 2007 though to 2010, Bricscad Pro v10

Laptop (Windows XP Pro v2002 SP3, x86) - all working well
Tower (Windows Vista Ultimate SP1, x86) - none work (controls not painting themselves on the tabs)

author=owenwengerd link=topic=1008.msg5151#msg5151 date=1258059199 wrote:
There is definitely a problem, but I'm not sure what the solution is.  For Alpha 13, I'll try making a few small changes to see if anything changes.

In 6.0.0.13 for me, the problem persists.
.. for both samples posted.

Regards
Kerry

Rats. :(

I don't know if this will help or not ...

The SlideControl MouseDown Event does not show buttons ( same as previous demo)
.. also does not add Text to textBox.

The  SlideControl FillImage is not contained in Slide Control .. spills over into form.

When the Piccy is selected when the current focus is on the SlideControl it takes 2 selections in the PiccyControl for the MouseDown event to be trapped.


Attached is a mini-Battleship Demo :)


Regards
Kerry

ps. Can we have a few people test this and report ..please.

The Video is set to run once. Refresh ( F5 ) the page to view again.

The LSP Source



(vl-load-com)
(command "OPENDCL")

;; Test Code 
;; 20091117 kdub@home

(defun c:doit () (c:test_1113B))

;|<>|;


;;;---------------------------------------------------------------------------
;;; (findfile "Test_1113B.ODCL")
;;;---------------------------------------------------------------------------
;;;
(defun c:test_1113B (/ dialogreturn)
  (dcl_project_load "Test_1113B.ODCL" t)
  ;; Show the main form 
  (setq dialogreturn (dcl_form_show test_1113B_main))
  ;;------ 
  (princ)
)
;;;---------------------------------------------------------------------------
;;;
;|<>|;
(defun _ManageSlideView (button flags x y / Sector)
  ;;
  ;; Slide control is set at 120x120
  (dcl_Control_SetText test_1113B_Main_XLocation (itoa X))
  (dcl_Control_SetText test_1113B_Main_YLocation (itoa Y))
  ;;Determine Sector
  ;; assume divisions 3 wide, 2 divisions high
  (cond ((< Y 60)                            ; The top half
        (cond ((< X 40) (setq Sector 1))
              ((< X 90) (setq Sector 2))
              (T (setq Sector 3))
        )
        )
        (T                                  ; Bottom Half
        (cond ((< X 40) (setq Sector 11))
              ((< X 80) (setq Sector 12))
              (T (setq Sector 13))
        )
        )
  )
  (dcl_Control_SetText test_1113B_Main_SectorText
                      (strcat "SlideSector " (itoa Sector))
  )
  ;;
  (dcl_control_setvisible test_1113B_main_textbutton2 t)
  (dcl_control_setvisible test_1113B_main_textbox2 t)
  ;;
  (dcl_slideview_fillimage test_1113B_main_slideview1
                          (list (list (- x 5) (- y 10) 10 20 3))
  )
  (dcl_slideview_endimage test_1113B_main_slideview1)
)
;;;-------------------------------------------
;;;
(defun _ManagePiccy (button flags x y / Sector)
  (dcl_control_setvisible test_1113B_main_textbutton1 t)
  (dcl_control_setvisible test_1113B_main_textbox1 t)
  ;;
  (dcl_picturebox_drawcircle test_1113B_main_picturebox1
                            (list (list (- x 15) (- y 15) 30 30 3))
  )
  (dcl_PictureBox_StoreImage test_1113B_Main_PictureBox1)
  ;;
  ;;
  ;; Piccy control is set at 120x120
  (dcl_Control_SetText test_1113B_Main_XLocation (itoa X))
  (dcl_Control_SetText test_1113B_Main_YLocation (itoa Y))
  ;;Determine Sector
  ;; assume divisions 3 wide, 2 divisions high
  (cond ((< Y 60)                            ; The top half
        (cond ((< X 40) (setq Sector 1))
              ((< X 90) (setq Sector 2))
              (T (setq Sector 3))
        )
        )
        (T                                  ; Bottom Half
        (cond ((< X 40) (setq Sector 11))
              ((< X 80) (setq Sector 12))
              (T (setq Sector 13))
        )
        )
  )
  (dcl_Control_SetText test_1113B_Main_SectorText
                      (strcat "PiccySector " (itoa Sector))
  )
)
;;;---------------------------------------------------------------------------
;;;
;|<>|;

(defun c:test_1113B_main_oninitialize (/)
  (dcl_control_setvisible test_1113B_main_textbutton1 nil)
  (dcl_control_setvisible test_1113B_main_textbox1 nil)
  (dcl_control_setvisible test_1113B_main_textbutton2 nil)
  (dcl_control_setvisible test_1113B_main_textbox2 nil)
  ;;
  (dcl_control_setbackcolor test_1113B_main_picturebox1 8)
)
;;;-------------------------------------------
;;;
(defun c:test_1113B_main_picturebox1_onmousedown (button flags x y /)
  (_ManagePiccy button flags x y)
)
;;;-------------------------------------------
;;;
(defun c:test_1113B_main_slideview1_onmousedown (button flags x y /)
  (_ManageSlideView button flags x y)
)
;;;-------------------------------------------
;;;
(defun c:test_1113B_Main_BtnReset_OnClicked (/)
  (dcl_control_setvisible test_1113B_main_textbutton1 nil)
  (dcl_control_setvisible test_1113B_main_textbox1 nil)
  (dcl_control_setvisible test_1113B_main_textbutton2 nil)
  (dcl_control_setvisible test_1113B_main_textbox2 nil)
  ;;
  (dcl_PictureBox_Clear test_1113B_Main_PictureBox1)
  (dcl_SlideView_Clear test_1113B_Main_SlideView1)
  ;;
  (dcl_Control_SetText test_1113B_Main_SectorText "")
  (dcl_Control_SetText test_1113B_Main_XLocation "")
  (dcl_Control_SetText test_1113B_Main_YLocation "")
)
;;;-------------------------------------------
;;;
(defun c:test_1113B_Main_ShowButtons_OnClicked (/)
  (dcl_control_setvisible test_1113B_main_textbutton1 T)
  (dcl_control_setvisible test_1113B_main_textbox1 T)
  (dcl_control_setvisible test_1113B_main_textbutton2 T)
  (dcl_control_setvisible test_1113B_main_textbox2 T)
)

;;;-------------------------------------------
;;;

;;;---------------------------------------------------------------------------
;;;

(prompt "\n Test_1113B ...  DoIt to run.")
(princ)

Hi I've tested on:

Tower, Windows Vista Ultimate SP1, AutoCAD 2010, Bricscad Pro v10
Laptop, Windows XP SP3, AutoCAD 2007 and Bricscad Pro v10

All issues were replicated with one difference:-

On the Vista machine - SlideControl MouseDown Event doesnot show the textbox either, however when the mouse is hoverred over it, it appears and indeed the text has been added to it (unlike for the XP machine where the textbox remains blank).

Thanks Danner .. much appreciated.

Something I didn't realise :

After selecting a point on the SlideView control the X Y and sector textboxes do not update.
.. However, if I click in each of those TextBos controls, the text updates with the correct data.

... ... seems like a focus thing, but thats a really wild guess :)

Hi, now with Alpha 13 I can reproduce it:

AMD Athlon XP 3200+, 1x2,2 GHz
2 GB of RAM
on MSI KT6 Delta-FISR (MS-6590 v2.0)
Windows XP DEU Version 5.1.2600 Service Pack 3 Build 2600
ATI Radeon 7500 DDR using Windows Driver (uses no CCC!)
DirectX 9.0Visual Style (Theme)
tried with WindowsXp Silver
-----

OpenDCL Runtime [6.0.0.13] in AutoCAD Civil 3D 2998 German

5123.png = OpenDCL 5.1.2.3
A13.png = OpenDCL 6.0.0.13

Fred

It turns out that the slide control blithely draws outside its boundary, even taking a snapshot of the surrounding controls and repainting whatever was in the snapshot. That problem should now be fixed in Alpha 14. Everything else appears to be working as well in Alpha 14, so it's possible that the other issues either got incidentally fixed, or they just don't happen on my configuration.

Thanks Owen !

With Build 6.0.0.14

test_1113B project works as expected.   wheee !!


The Test60012b project ( with the TAB Control and 3 pages ) still does not work.
I'll try to post a better description of the issues.

Best Regards
Kerrry

When each tabPage is displayed, it is empty except for the TextBox outline.
The TextBox will only display completely after a Click at it's location,

The TextButton will only display after a MouseOver or Click at it's location.

The GraphicButtom will only display after a Click at it's location
OR after a click in the textBox
OR after a click in the textButton.



regards
kerry

code is in the first Post.

The Video is set to run once. Refresh ( F5 ) the page to view again.

author=Kerry Brown link=topic=1008.msg5213#msg5213 date=1258968322 wrote:
The Test60012b project ( with the TAB Control and 3 pages ) still does not work.
I'll try to post a better description of the issues.

Yep, same problem for me on Vista. XP still fine. 

(Test_1113B working great on both)

whereas I have the issue on XP sp3 (don't use vista)

Oh oh, do I have to change anything? It's getting worse in Alpha 14.
The bullet and the textbox appear only after mouseover. The textbox stays grey (although it should never be grey) and the picture box in the textbox is missing.

Picture Top: Stable release 5.1.2.3
Picture Bottom: 6.0.0.14

Fred

I've made some changes for Alpha 15 that might fix this (or make it worse!).

Owen, I have the feeling that it is better (see ltm.gif). The caption will be displayed correctly in 5.1.2.3 (filled during OnInitialize). In 6.0.0.15 I have to set the caption manually after OnInitialize.

Another thing I recognized:
I have some picture buttons on the first tab which are disabled. As you can see in FormOver.gif they are overlayed with the form which is above during initialisation (here: OPM). Unfortunately, I have no chance to influence this. It is not so, if no other form is above.

Fred

6.0.0.15 - I'm afraid the problem with display of controls on tabs, see with Kerry's Test60012b project - still persists with my (Vista) computer.  My (xp) laptop still working fine. 

author=Danner link=topic=1008.msg5376#msg5376 date=1259580330 wrote:
6.0.0.15 - I'm afraid the problem with display of controls on tabs, see with Kerry's Test60012b project - still persists with my (Vista) computer.  My (xp) laptop still working fine. 

Ditto ...  but I'm using XP sp3. frustrating.

Fred, it would be helpful if you could attach simple examples (modeless form with bare minimum controls) that demonstrate each remaining problem.

Hi, Owen,

for the issue with overlaying form I send you an example:

• Load the project I attached. You won't need any code.


• (dcl_form_show demo1_dialog1)


• If no form lies over the sample palette everything seems to look fine.


• Open AutoCAD object property manager and move it over the sample palette.


• Close the sample palette


• Open the sample palette again. Some controls show the pixels of the covering form.

Fred

Owen, the first problem I mentioned on top (with the disappearing caption) I cannot reproduce at my Win7 x64 Bit Notebook in a small project. But I'm just on tour these days. I'll try to create a new sample on thrusday when I'm back in office. Then I will also have a try to describe another new effect I had with one of my modeless form in Alpha 15: it "forgot" all its properties (but not Height and Width) so I had to reload the project file anew that all the other properties (like TitleBarText) are present again. But I think I need more silence to reproduce and to describe this. So I ask you for patience until thursday.

Fred

I could not reproduce the problem with your demo1 sample in Windows 7 x64 and AutoCAD 2010. It would be better if you can reproduce it with a modeless form that has only one control on it. Your sample introduces extra factors (pallete form, tab page, multiple controls) which could have an impact. By narrowing the problem down to the bare minimum needed to reproduce it, you will save me a lot of time chasing dead ends.

Owen, I have just created a modeless form with only the four imagebuttons. In that combination the effect you can see at the screenshot does not appear. The reason might be that the modeless form pushes itself to front automatically when form_show will be called.

This may be the difference to the palette form of my demo1-sample: Since the palette will be docked automatcally when Form_Show will be called it may appear behind an open floating palette. That's why I created a small example with the contents where I can reproduce.

Fred

I tested with the demo1 palette floating. Does it need to be docked?

No, but there has to be another palette over the position where the demo1 palette will appear. If the demo1 palette appears behid the other palette it should be reproducable (so on my Win7 x64 notebook). Will the demo1 palette not be docked if you call it? It is is docked at my notebook whatever I do.

Fred

The demo1 palette was docked initially, but I thought from your description that it should be floating, so I undocked it for testing.  Let me know if you think of anything else I can try.

NOTE: Issues raised in this thread were related to a particular series of builds where the control painting methodology was being redesigned.
These issues have now been RESOLVED.
kwb.
///------------------------------------------------------------------------------------------