layer Posted April 15, 2005 Share Posted April 15, 2005 im doing some work on my HTML code generator and im doing the hard code editing (where the edit becomes NON readonly) and heres what ive got, and tried but doesnt work Func _SetHardCodeStyle() If GUICtrlRead($hardcode) = $GUI_CHECKED then GUICtrlSetStyle($output, -1) Else GUICtrlSetStyle($output, $ES_READONLY) EndIf EndFunc yes yes, the variables are declared, so basically, if the checkbox is checked, and the button (not in this code) is pressed, then set the main edit control ($output) to default styles, and NOT readonly.. else, just make it read only.. and yes, ive tried putting a msgbox where GUICtrlSetStyle is and the msgbox appears, so everything is working except for this.. and heres the othetr thing i tried: Func _SetHardCodeStyle() If GUICtrlRead($hardcode) = $GUI_CHECKED then GUICtrlSetStyle($output, NOT $ES_READONLY) Else GUICtrlSetStyle($output, $ES_READONLY) EndIf EndFunc Any suggestions... thanks FootbaG Link to comment Share on other sites More sharing options...
layer Posted April 15, 2005 Author Share Posted April 15, 2005 *bumpzorz* FootbaG Link to comment Share on other sites More sharing options...
buzz44 Posted April 15, 2005 Share Posted April 15, 2005 If GUICtrlRead($checkCN) = $GUI_CHECKED then GUICtrlSetStyle($output, $WS_DISABLED) Else GUICtrlSetStyle($output, $GUI_ENABLE) EndIf That sorta works. I tested that on an Inputbox, which I am assuming $output is. The only problem is that when the Check box is checked and $WS_DISABLED is active you cant highlight whats in the inputbox. qq Link to comment Share on other sites More sharing options...
layer Posted April 15, 2005 Author Share Posted April 15, 2005 wtfeck is $WS_ENABLED and $WS_DISABLED?? those arent even in GUIConstants.au3... obviously then you didnt check it, unless im missing something in my include?? i tried $GUI_ENABLE, and that doesnt work either... FootbaG Link to comment Share on other sites More sharing options...
buzz44 Posted April 15, 2005 Share Posted April 15, 2005 (edited) I didn't say anything about $WS_ENABLED, and yes I did check it...$WS_DISABLED 0x08000000 Creates a window that is initially disabled. Why dont you open up the GUI Control Styles Tab....Edit: I suppose you could do something abit... messy and create a new one each time$check = 1 If GUICtrlRead($checkCN) = $GUI_CHECKED then If $check <> 0 Then GUICtrlDelete ($output) $OutPut = GUICtrlCreateInput ( "text", left, top -1, -1) $check = 0 EndIf Else If $check <> 1 Then GUICtrlDelete ($output) $OutPut = GUICtrlCreateInput ( "text", left, top -1, -1, $ES_READONLY) $check = 1 EndIf EndIf Edited April 15, 2005 by Burrup qq Link to comment Share on other sites More sharing options...
Valik Posted April 15, 2005 Share Posted April 15, 2005 I don't think its terribly unreasonable for a user who is having problems with a style to consult the authoritative resource for Windows programming: MSDN. Spending about 5 seconds looking up the style ES_READONLY yielded me this information:ES_READONLY Prevents the user from typing or editing text in the edit control.To change this style after the control has been created, use the EM_SETREADONLY message. Link to comment Share on other sites More sharing options...
layer Posted April 16, 2005 Author Share Posted April 16, 2005 thanks.. works perfect FootbaG Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now