why listview scroll bar is on the left ?

[Edano]

#include <GuiListView.au3>

$RA_GUI=GUICreate("",700,500)
$RA_ListView=GUICtrlCreateListView("Bild-Nr.|Name|Vorname",10,50,680,408,BitOR($LVS_SHOWSELALWAYS,$LVS_SINGLESEL),BitOR($LVS_EX_GRIDLINES,$LVS_EX_FULLROWSELECT,$LVS_EX_CHECKBOXES,$LVS_EX_LABELTIP))

For $i=0 To 100
    GUICtrlCreateListViewItem($i,$RA_ListView)
Next

GUISetState()


While GUIGetMsg()<>-3
WEnd

.

without $LVS_EX_LABELTIP it's right, on the right. how to fix it ?

 

thx

E

[Melba23]

Edano,

It happens because some $LVS_EX_* styles have the same values as various $WS_EX_* styles and so they are interpreted as extended GUI styles if they are applied when you create the control. I recommend that you always use _GUICtrlListView_SetExtendedListViewStyle to set $LVS_EX_* styles - you get the scroll bar on the right then:

#include <GuiListView.au3>

$RA_GUI=GUICreate("",700,500)
$RA_ListView=GUICtrlCreateListView("Bild-Nr.|Name|Vorname",10,50,680,408,BitOR($LVS_SHOWSELALWAYS,$LVS_SINGLESEL))
_GUICtrlListView_SetExtendedListViewStyle($RA_ListView, BitOR($LVS_EX_GRIDLINES,$LVS_EX_FULLROWSELECT,$LVS_EX_CHECKBOXES,$LVS_EX_LABELTIP))

For $i=0 To 100
    GUICtrlCreateListViewItem($i,$RA_ListView)
Next

GUISetState()

While GUIGetMsg()<>-3
WEnd

All clear?

M23

[Edano]

Edano,

It happens because some $LVS_EX_* styles have the same values as various $WS_EX_* styles and so they are interpreted as extended GUI styles if they are applied when you create the control. I recommend that you always use _GUICtrlListView_SetExtendedListViewStyle to set $LVS_EX_* styles - you get the scroll bar on the right then:

#include <GuiListView.au3>

$RA_GUI=GUICreate("",700,500)
$RA_ListView=GUICtrlCreateListView("Bild-Nr.|Name|Vorname",10,50,680,408,BitOR($LVS_SHOWSELALWAYS,$LVS_SINGLESEL))
_GUICtrlListView_SetExtendedListViewStyle($RA_ListView, BitOR($LVS_EX_GRIDLINES,$LVS_EX_FULLROWSELECT,$LVS_EX_CHECKBOXES,$LVS_EX_LABELTIP))

For $i=0 To 100
    GUICtrlCreateListViewItem($i,$RA_ListView)
Next

GUISetState()

While GUIGetMsg()<>-3
WEnd

All clear?

M23

.

thank you ! i have often seen that, but never an explanation. thx

E

[guinness]

It's also recommended to use $GUI_EVENT_CLOSE found in GUIConstantsEx rather than -3, as it's easier to read and common practice. You can find out more by searching about 'magic numbers'.

[Edano]

It's also recommended to use $GUI_EVENT_CLOSE found in GUIConstantsEx rather than -3, as it's easier to read and common practice. You can find out more by searching about 'magic numbers'.

.

personally, i do not agree to that. i prefer -3 for several good reasons.

[guinness]

.

personally, i do not agree to that. i prefer -3 for several good reasons.

OK, and your reasons are? I'm actually interested and then I will provide my reasons why they are bad.

[Edano]

well, really ?

-3 is easier to write. i don't need to know the includes file, which has often changed in autoit history. -3 will always be true, while autoit changes. i can use mathematical conversions on numbers, e.g. GuiCtrlSetState(-1,128-64*($flag=1)) to avoid if thens. i tought myself over the years to learn the most common values by heart. i can use years old scripts without getting constant-not-declared errors.   .....

E

[AdmiralAlkex]

There has been 1 majorish change of the includes since I joined and I don't know if that specific const was part of it. I wouldn't call it often.

[guinness]

Sounds more like you're making life difficult for yourself. I can't remember what -14 is as an event for GUIGetMsg, so you're smarter than I am Edano.

Please don't try and force people to convert to your approach in the Forum, this will lead to even more questions. Thanks. 

My arguments:

1. $GUI_EVENT_CLOSE is easier to remember than -3.

2. Debugging is way easier, because -3 in one area of the code might be a number and not an event & vice-versa.

3. AutoIt could internally change any of the constant values in a second. Probably won't happen but you never know.

4. Changing a single value is far easier on a global scale. What if you have a constant for 5001? Replace will replace all instances of 5001 that might not be reference to that particular 'constant'.

5. Less change of a typo happening.

Edited June 23, 2013 by guinness

[guinness]

Just did a quick search and found this blog >> http://blogs.msdn.com/b/alfredth/archive/2012/02/14/magic-numbers-are-bad.aspx?Redirected=true

[Edano]

oh no, i wouldn't force anyone i wouldn't even use the indeed complicated gui style values without commenting them, but some basic values are good to know. $GUI_CHECKED and $GUI_UNCHECKED for example, hidden / shown, disabled / enabled. the daily stuff. used with common sense.

[guinness]

oh no, i wouldn't force anyone

Good. Thamks for listening.