Gui with slim border

[Chimaera]

Im messing with a gui like this

#include <GUIConstantsEx.au3>
#include <WindowsConstants.au3>
#include <Constants.au3>

$hGui = GUICreate( "", 465, 136, -1, -1, $WS_BORDER)
$hButton1 = GUICtrlCreateButton( "", 21, 23, 70, 70)
$hButton2 = GUICtrlCreateButton( "", 109, 23, 70, 70)
$hButton3 = GUICtrlCreateButton( "", 197, 23, 70, 70)
$hButton4 = GUICtrlCreateButton( "", 285, 23, 70, 70)
$hButton5 = GUICtrlCreateButton( "", 373, 23, 70, 70)
GUISetState()

While 1
$hMsg = GUIGetMsg()
Switch $hMsg
Case $GUI_EVENT_CLOSE
Exit
EndSwitch
WEnd

If you run this example it has a slim border all round the bottom and each side is it possible to get that border all round the gui?

I tried $DS_MODALFRAME / $WS_DLGFRAME / $WS_BORDER

But i need it to affect the top bar as well and optional have square edged corners as it will be a windows 8 only script

Any thoughts?

Edited February 13, 2013 by Chimaera

[guinness]

I also corrected the structure of your example, as this is how I would do it personally. 0_-

#include <GUIConstantsEx.au3>
#include <WindowsConstants.au3>

Example()

Func Example()
    Local $hGUI = GUICreate('', 465, 135, Default, Default, BitOR($WS_THICKFRAME, $WS_POPUP))
    GUISetState(@SW_SHOW, $hGUI)

    GUIRegisterMsg($WM_NCHITTEST, 'WM_NCHITTEST')

    While 1
        Switch GUIGetMsg()
            Case $GUI_EVENT_CLOSE
                ExitLoop
        EndSwitch
    WEnd

    GUIDelete($hGUI)
EndFunc   ;==>Example

; If you want the GUI to be moved as well.
Func WM_NCHITTEST($hWnd, $iMsg, $wParam, $lParam)
    #forceref $hWnd, $iMsg, $wParam, $lParam
    Return $HTCAPTION
EndFunc   ;==>WM_NCHITTEST

Edited February 13, 2013 by guinness

[Chimaera]

It was pretty much as i took it from FormBuilder m8 i hadn't really got started tweaking.

Im assuming by corrections you mean no -1 and use default?

Do you always make a gui in a function?

Just lately there seems to be different code popping up all over in threads which i know nothing about..

I get Autoit is evolving towards being a proper language but it feels sometimes like its moving away from the non programmers domain into serious geek stuff.

Thx anyway now i just got to work out how to colour the edges the same as the inner bit

[BrewManNH]

None of the changes made will affect how the script works in AutoIt. You can continue coding in the same way as you normally do.

[guinness]

The answer is yes or I least make sure I avoid using Global variables if I can. I once didn't care about good coding standards in AutoIt because no one bothered to talk about it in the Forums/Wiki. Some people are against my methods and that's fine, I just want show people that good code can be written and that we aren't just a bunch of (I hate this term) newbs who know very little about coding.

Anyway, I will continue to post the way I do and hopefully it will teach someone or make people think differently about AutoIt. I know I've learnt a lot in the last 12 months of the dos and don'ts with peroper coding.

Thx anyway now i just got to work out how to colour the edges the same as the inner bit

You can't do that with what I presented above. Edited February 13, 2013 by guinness

[guinness]

None of the changes made will affect how the script works in AutoIt. You can continue coding in the same way as you normally do.

Well not completely true, but Chimaera can decide what to use and what not to use.

[Chimaera]

I think the thing that confuses me and prob some others is it filters in in dribs and drabs, i was reading the convo you were having earlier about default , thats how i knew about it.

If there was for e.g. latest change section Now you must use Default instead of -1 thread. << just an e.g.

We would know its something we need to change, as I see little mentions here and there I have no idea is it implemented ? or not ?, it could just be 2 members discussing an opinion.

There has been a number of things like that lately, BitOr etc was another one it seems mandatory to use a a Bit something these days and i have no idea whether its necessary as again it grew out of little convos here and there, and then all of sudden its here.

That how it appears to me. Prob because i dont understand the bigger picture who knows, i certainly dont understand any other languages

You can't do that with what I presented above.

Just read this line

Only Button, Label, Checkbox, Group, Radio, Edit, Input, List, Listview, ListviewItem, Treeview, TreeviewItem, Graphic, Progress and Combo controls can currently be colored.

Feck thats that idea out the window, i was trying to make a win 8 style smooth to the edges gui..

@guinness As to your coding teaching style m8, my stuff wouldn't be half as good now if it wasn't for your help

Edited February 13, 2013 by Chimaera

[BrewManNH]

Just an FYI, in the built-in functions, Default and -1 have the same meaning, not so much so in the UDFs though, there if it says use -1then use -1 unless you look at the function and see that it will accept Default in its place.

[Chimaera]

Im assuming Default is being adopted because it is less problematic with things that use -1 like UDF's

[BrewManNH]

Some of the bugs in the UDF functions came about because the authors used -1 or 0 as a default value (instead of using the Default keyword) when the function should be able to use those values as input, such as the bug in _FileWriteFromArray where you couldn't write the zeroth element of an array by itself, because the function needed a start element and an end element as options, and if you used 0 in the end element the function assumed you meant the whole array instead of the first element.

Other than that, some people don't like the look of using -1 to denote a default value, even when it's valid.

[guinness]

Just an FYI, in the built-in functions, Default and -1 have the same meaning, not so much so in the UDFs though, there if it says use -1then use -1 unless you look at the function and see that it will accept Default in its place.

This should be changed in the next version of AutoIt as I've gone through quite a few of the UDFs so they now accept Default keyword.

Chimaera,

By all means use -1, but personally I use Default if I want to use the default parameters of that function. It just so happens that the default parameter for the GUICreate left and top is -1, but if for example it was -123456789 as the default parameter, then you wouldn't need to remember that complex number as you would use the Default keyword. Understand? If not let me know.

It's not my nature to confuse people, I just want to get people interested in exploring AutoIt's uses further and people going out of their comfort zone.

Edited February 13, 2013 by guinness

[Chimaera]

Thx for the info

Im guessing Autoit as whole is still full of little inconsistences that trancexx and the others iron out over time.

I know what my code is like sometimes, it must be a nightmare handling autoit itself

@guinness no i get it, it makes sense to have an easily identifiable setting, makes it easier when people post as well id imagine, it just the way it sneaks into the lingo that confuses me..

[guinness]

_FileWriteFromArray

That was the first function that came to my mind when discussing about Default and -1.

[guinness]

I know what my code is like sometimes, it must be a nightmare handling autoit itself

Don't get me wrong, I'm far from perfect and that's the sole reason I'm posting in General Help and Support these days asking "Is this right or is this wrong, could it be better, what is the standard practice?" because the only language I have ever really got to grips with is AutoIt (+ some VBScript/Batch commands) so I don't have a coding background per say.

Edit: Re-worded.

Edited February 13, 2013 by guinness

[guinness]

I will commend you Chimaera on paying attention to what happens around here, you never know maybe one day it will come in quite handy.

[Chimaera]

I try and follow the broad view of AutoIt, i never comment much because most is way over my noodle.

Anyway thx guys for a stimulating mostly off topic thread in which the answer was found