Issue 7459 - ComboBox ListBox are buggied when PageUP PageDOWN used
Summary: ComboBox ListBox are buggied when PageUP PageDOWN used
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Linux, all
: P3 Trivial
Target Milestone: ---
Assignee: marc.neumann
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-03 03:06 UTC by Unknown
Modified: 2013-02-24 21:08 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-09-03 03:06:15 UTC
Try to create a library Test with a simple Dialog1
In the dialog create a ComboBox ( that's dropdown as default )
Use follow code to creates 3000 items in the combo
The combo has to be the first in the order so when the dialog
starts the combo has the keyboard focus
Start the dialog, then try to use PageDOWN ( without opening the dropdown list
), works ? for me no, I you try to use DOWN key sometimes, this works, but
when you try PageDOWN now, you get an UP key behavior.
Right, this bug doesn't happen if you open the dropdown list before
testing this thing.

Last note: this test is done using addItems with a variant array dimensioned
variable.

THE CODE:

REM  *****  BASIC  *****

Sub Main
	Dim dialog1 As Object
	dialog1 = LoadDialog( "Test", "Dialog1" )
	
	Dim combo As Object
	combo = dialog1.getControl( "combo" )
	
	Dim items As Variant
	Dim i As Long
	
	items = DimArray( 3000 - 1 )
	
	For i = 0 To ( 3000 - 1 )
		items( i ) = "item_" + Format( i, "0" )
	Next i
	
	combo.addItems( items, 0 )
	
	dialog1.Execute()
End Sub

Function LoadDialog(Libname as String, DialogName as String, Optional
oLibContainer)
Dim oLib as Object
Dim oLibDialog as Object
Dim oRuntimeDialog as Object
If IsMissing(oLibContainer ) then
oLibContainer = DialogLibraries
End If
oLibContainer.LoadLibrary(LibName)
oLib = oLibContainer.GetByName(Libname)
oLibDialog = oLib.GetByName(DialogName)
oRuntimeDialog = CreateUnoDialog(oLibDialog)
LoadDialog() = oRuntimeDialog
End Function
Comment 1 ooo 2002-12-19 10:49:58 UTC
I am not sure, whose bug this is, my guess is yours, Frank?
Comment 2 Frank Schönheit 2002-12-19 13:17:11 UTC
Thomas, this sounds like either a problem of the underlying VCL
control, or it's toolkit representation. In both cases, I assume,
you're a good person to have a look at it.
Comment 3 Frank Schönheit 2002-12-19 13:33:33 UTC
now really changing ownership ....
Comment 4 thomas.benisch 2003-01-06 15:46:04 UTC
TBE->SSA: The problem seems to be in 
ImplListBoxWindow::ProcessKeyInput, case KEY_PAGEUP/KEY_PAGEDOWN.
Comment 5 stephan_schaefer 2003-01-07 12:26:15 UTC
I'll have a look...
Comment 6 stephan_schaefer 2003-01-30 15:06:50 UTC
The number of visible lines were not computed until the combobox or 
listbox popped up the first time. Can also be seen easily in combo- 
or listboxes in the toolbar. PageUp/PageDn behaved differently once 
you opened the list box. Fixed now in CWS vcl04.
Comment 7 stephan_schaefer 2003-02-05 17:56:09 UTC
reopen
Comment 8 stephan_schaefer 2003-02-05 17:59:03 UTC
please verify in vcl04.
Comment 9 oc 2003-02-11 09:40:05 UTC
Hi Marc, please have a look at this
Comment 10 oc 2003-02-11 09:40:45 UTC
Reset status
Comment 11 ulf.stroehler 2003-02-12 13:15:52 UTC
Component: api. Transferring to SW.
Have to reopen first.
Comment 12 ulf.stroehler 2003-02-12 16:41:15 UTC
setting back to fixed.
US: The initial problem was when selecting a combo box (e.g. in Draw,
in the Object Bar - Line Color combo box) by  keyboard shortcut F6.
Now hitting Return (to select it) and page down only scrolled down one
item, as if cursor down was pressed. (Page down was calculated correct
ever since the combo box was dropped down once - by mouse.) This has
now been corrected.
No need for transferring.
Ok in vcl_04
Comment 13 ulf.stroehler 2003-02-12 16:42:04 UTC
.
Comment 14 marc.neumann 2003-02-23 15:45:15 UTC
ok in m4s4
Comment 15 michael.bemmer 2003-03-13 11:11:30 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.