Jump to content

mdes

Active Members
  • Posts

    48
  • Joined

  • Last visited

Profile Information

  • Location
    Sucy en Brie - France
  • WWW
    http://congesrfv.free.fr

mdes's Achievements

Seeker

Seeker (1/7)

0

Reputation

  1. LostZXC perhaps, but not me... at least before reading your reply: Thanks a lot Zulu! Michel
  2. Here is the generated GUI (context menu is not shown):
  3. Hi everybody, I do never want to reinvent the wheel. That's why after waiting some times without seeing a GUI builder with a lot of possibilities, like the Visual Studio IDE, I start the job of converting the VB.Net Form Design file to AutoIt GUI management. Here is a first result: VB2AutoItGUI Name: VB2AutoItGUI Function: Generate a GUI management file from a VB.Net Form design file (GUI Builder) Purpose: The purpose of VB2AutoItGUI is to allow a user to create a GUI with a free program (VB.Net Express), and to generate automaticaly the AutoIt GUI for this form. The VB.Net form could be modified and generated again, and again. Parameters: (if missing, it is asked) 1. Input file name 2. Output file name Notes: VB2AutoItGUI is not yet finished: there is still some attributes to generate (see the log file). The Icon and AVI does not exist in VB.Net, so, you should use the PictureBox, and the Tag attribute should contain some parameters: For an Icon(resp. AVI), the Tag should contain ICO (resp. AVI). It could also contains some parameters (ex: Me.PictureBox2.Tag = "AVI,$ACS_AUTOPLAY"). Creation time: Inputs: - The input file which contain the VB.Net form design (e.g. Form1.Designer.vb). Output: - The file containing the GUI definitions. The Function to call is: FormName_GUI(). - The log file (= OuputFileName.log). It contains le list and the tree of all objects. The lines starting with "Attribute not processed", indicate a VB.Net attributes which is not yet processed by this version of VB2AutoItGUI. - The file VB2AutoItGUI.ini wich will contain the input and the output filenames. When running the generated form, the following files are required: (i.e. #include's are generated) 1. The output file 2. <FormName>_def.au3: It mut define the value for some variables (icons filename,...). The log file indicates which variable are required to be defined. 3. <FormName>_evt.au3 This file is include before the loop on the GUI event. So, you can change the evnt processing. (Donot forget to GUIDelete() at the end. A simple loop is generated, and can be used as a template. Example: The attached example contains the definition of the forms given in the AutoIt help. Tests: You can test the output file by creating 1. The file with the required definitions <FormName>_def.au3. (See the generated log file) Ex: (used for the AutoIt GUI example) $SampleControls_Icon = @SystemDir & "\mspaint.exe" $SampleControls_IconNr = 0 $PictureBox1_Image = "logo4.gif" $PictureBox2_AVI = "sampleAVI.avi" $PictureBox2_SubFileID = 0 $PictureBox3_Icon = "shell32.dll" $PictureBox3_IconNr = 1 3. an empty file <FormName>_evt.au3 So, you may test quickly the generated GUI. 2. A file containing the following lines: #include "OutputFilename" FormName_GUI() History: v0.1 2007/02/13 - Released to to AutoIt forum users. Author: Michel Dessaintes (Nick: mdes)VB2AutoItGUI.zip
  4. I'm often using FOR..IN, but there is no object grouping the labels, nor the tips; so, I will keep the controlsID's in a array and delete them in a FOR GUICtrlDelete(ControlID) loop... as I said in my first post.
  5. Not enough, I will have to delete also the Tips. So, I will delete them with an array and a For Loop I would like to have something like For each $label in gui.Labels or GUI.Labels.Collection.Clear : Don't forbid me to dream Thanks for yours contributions
  6. In my application, I draw a lot of labels (+ a tooltip for every of each). I would like to delete all of them; is there another way instead of keeping in an array all the returned controlID, and to loop on all GUICtrlDelete()? In fact, I would like to erase all the labels, but this cannot be done without GUICtrlDelete(). Thanks for any advice
  7. GUICtrlSetGraphic(): Error while beta-compiling:D:\Program Files\AutoIt3\beta\Examples\Helpfile\GUICtrlSetGraphic.au3(41,51) : ERROR: GUICtrlSetGraphic() [built-in] called with wrong number of args. GUICtrlSetGraphic(-1,$GUI_GR_PIE, 50,50, 40,30,270) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^When continuing after the error, the .EXE seems OK.
  8. Following is a code showing a label partially over a Graphic. The Tip is not shown when the mouse is on the label part which is overlayed by the graphic: #include <GUIConstants.au3> $GUI = GUICreate("My GUI control tip", 150, 120); will create a dialog box that when displayed is centered $Graphic = GUICtrlCreateGraphic (0, 0, 60, 120) GUICtrlSetBkColor(-1, 0xff0000) GUICtrlCreateLabel("my label", 40, 40) GUICtrlSetTip(-1, "tip of my label") GUISetState() While GUIGetMsg() <> $GUI_EVENT_CLOSE WEndIs it normal? Edit: I solved the problem by adding GUICtrlSetState(-1, $GUI_DISABLE) for the graphic
  9. Thanks a lot
  10. Is it possible to install the updates silently (/S is still asking "a lot" of questions)? Thanks, Michel.
  11. I just discovered it
  12. @JdeB: Thanks for all the improvments, it's really lovely to developp with SciTE Now, I'm waiting the integration of v3.1.1.18 to have TrayDeleteItem() working
  13. I don't agree: "sShortDate" will give "dd/MM/yyyy" or "MM/dd/yyyy" depending on the country; so my application would not be able to process directly the date without analyzing this "sShortDate" But I fully agree to read the Registry for "sLongDate", and in any other case
  14. Thanks a lot, Randall, that's exactly what I wanted Thanks also to jpm for its proposal but Randall found it
  15. Thanks for your quick reply, but - as I said - I would like to keep the default format displayed "day d mmmm yyyy". The problem is "How to display a format, but getting back another one?"
×
×
  • Create New...