Strange Vista problem with Editor gadget!

[srod]

No problem on XP, but the following on Vista throws up a strange problem :

Code: Select all

If OpenWindow(0, 0, 0, 322, 150, "EditorGadget", #PB_Window_SystemMenu | #PB_Window_ScreenCentered)
  hWnd = EditorGadget(0, 8, 8, 306, 73)
  For a = 0 To 5
    AddGadgetItem(0, a, "Line "+Str(a))
  Next
  ButtonGadget(1, 10, 100, 80, 20, "CLICK!")
  Repeat
    ev = WaitWindowEvent()
    If ev =#PB_Event_Gadget
      If EventGadget() = 1
        ClearGadgetItems(0)
      EndIf
    EndIf
  Until ev = #PB_Event_CloseWindow
EndIf

Run the code and scroll the editor right down to the bottom of the control. Now hit the button to clear the contents and, on my system at least, the scrollbar is still visible (although it is invalidated!) This only happens with the Aero theme etc.

My suspicion is that the editor gadget has a timer running for some reason which is reinstating the scrollbar before it finishes. With a suitable delay I can remove the scrollbar easily enough, but this is damn annoying!

Can someone else running Vista confirm this please before I try to find a workaround. I'd be interested also to see if this is a problem on Win 7 if someone could try it out for me?

Thanks.

[ts-soft]

I think it is a problem with your driver for graficcard.

[Arctic Fox]

I can confirm this on Vista 32-bit - but only when scrolling down with the scrollbar itself (not with Page Down or the mouse wheel).

[srod]

I think it is a problem with your driver for graficcard.

I have a workaround of repositioning the scrollbox and so, well, I doubt whether this is a driver problem - unless you cannot confirm the problem on your system?

[ts-soft]

No problem on vista 64

[srod]

Right, let me try Vista 64. I have to reboot for that.

[srod]

Same problem under Vista 64. If it is a driver problem then it is inherent within both the 32-bit and 64-bit drivers. I am using the latest version of the 64-bit driver.

Very strange indeed. Especially as Arctic Fox reports the same problem.

[Arctic Fox]

I have got the same problem with the EditorGadget-example from PureBasic's help file.
Insert some blank lines until the scrollbar gets visible. Delete those lines again. Sometimes the scrollbar disappears, sometimes it doesn't

Code: Select all

  If OpenWindow(0, 0, 0, 322, 150, "EditorGadget", #PB_Window_SystemMenu | #PB_Window_ScreenCentered)
    EditorGadget(0, 8, 8, 306, 133)
    For a = 0 To 5
      AddGadgetItem(0, a, "Line "+Str(a))
    Next
    Repeat : Until WaitWindowEvent() = #PB_Event_CloseWindow
  EndIf

[srod]

I have got the same problem with the EditorGadget-example from PureBasic's help file.
Insert some blank lines until the scrollbar gets visible. Delete those lines again. Sometimes the scrollbar disappears, sometimes it doesn't

Code: Select all

  If OpenWindow(0, 0, 0, 322, 150, "EditorGadget", #PB_Window_SystemMenu | #PB_Window_ScreenCentered)
    EditorGadget(0, 8, 8, 306, 133)
    For a = 0 To 5
      AddGadgetItem(0, a, "Line "+Str(a))
    Next
    Repeat : Until WaitWindowEvent() = #PB_Event_CloseWindow
  EndIf

Unable to confirm that one.

I have just installed the latest video drivers from Intel and no difference. Got to say that this looks like a bug with Vista rather than anything else.

Still, whilst there's a workaround or two, who's complaining!

[ts-soft]

Using OnBoardGrafic or slow RAM with AERO is a problem and work not at
all correct.
For some month i have used my on board GeForce7 and 667 MHz RAM,
many problems with Video and so on (Bluescreens by 1080p HD Video).
After adding a real Graficcard and better RAM no more problems.

For AERO is required a fast RAM and a middleware Graficcard, to work
correct with VISTA.

I think is a hardwareproblem, i have no problems with your snippet.

[Fluid Byte]

Run the code and scroll the editor right down to the bottom of the control. Now hit the button to clear the contents and, on my system at least, the scrollbar is still visible (although it is invalidated!) This only happens with the Aero theme etc.

Confirmed on Vista Home Premium 64-Bit. This doesn't look like a driver issue.

[srod]

Using OnBoardGrafic or slow RAM with AERO is a problem and work not at
all correct.
For some month i have used my on board GeForce7 and 667 MHz RAM,
many problems with Video and so on (Bluescreens by 1080p HD Video).
After adding a real Graficcard and better RAM no more problems.

For AERO is required a fast RAM and a middleware Graficcard, to work
correct with VISTA.

I think is a hardwareproblem, i have no problems with your snippet.

Sounds very plausible Thomas. My machine has 2 GB of DDR2 RAM (I don't know how to figure out the speed of the RAM) but the integrated graphics uses 128 MB of shared memory.

I have confirmed the use of a timer by the editor gadget and it just doesn't seem to finish whatever it is doing in time! Suggests that you are indeed correct!

[Fluid Byte]

Using OnBoardGrafic or slow RAM with AERO is a problem and work not at all correct.

Nonsense. I have 8 GB of RAM and a GT 130 with 1.5 GB memory.

[ts-soft]

Using OnBoardGrafic or slow RAM with AERO is a problem and work not at all correct.

Nonsense. I have 8 GB of RAM and a GT 130 with 1.5 GB memory.

Oh, i have never seen a GT 130 OnBoard

[Fluid Byte]

Oh, i have never seen a GT 130 OnBoard

You point is hardware, that has nothing to do with it. Also I don't have "slow" RAM. So that simply isn't the source of the problem.