| View previous topic :: View next topic |
| Author |
Message |
majkinetor
Joined: 24 May 2006
Posts: 3644
Location: Belgrade
|
 Posted: Wed Jun 13, 2007 8:08 am Post subject: |
 |
|
BTW, I think we should create custom Tab control.
This internal one seems to be pain.
This can be presented as general container - Panel is single tabed Tab without tab button.
We can always put it the way so contanier can be added to container, something not very nice to do in AHK.
_________________
 |
|
| Back to top |
|
 |
majkinetor
Joined: 24 May 2006
Posts: 3644
Location: Belgrade
|
| Posted: Wed Jun 13, 2007 8:31 am Post subject: |
|
|
This is solution for docking:
1. Return docking ON, desable moving restriction.
2. Add new message handler in Messages_SetHandlers
| Code: | , WM_MOVING := 0x216
OnMessage( WM_MOVING, "Messages_OnMove") |
3. Hide selector on moving:
| Code: | Messages_OnMove(wparam, lparam, msg, hwnd) {
if Selector_visible
Selector_Hide()
} |
_________________
|
|
| Back to top |
|
|
majkinetor
Joined: 24 May 2006
Posts: 3644
Location: Belgrade
|
| Posted: Wed Jun 13, 2007 8:44 am Post subject: |
|
|
I checked in VS.
This resizing thingie with small windows is OS bug. Probably nobody used GUIs for applications of this kind 
_________________
|
|
| Back to top |
|
|
toralf
Joined: 31 Jan 2005
Posts: 3841
Location: Bremen, Germany
|
| Posted: Wed Jun 13, 2007 9:43 am Post subject: |
|
|
| majkinetor wrote: | | Quote: | | Is there a way to detect a click in the title of the gui and hide the selector on this? |
Yes. We have to monitor NC (non client area) messages. |
Can you show me how?
| majkinetor wrote: | | Quote: | | How to store and return it elegant is the question. |
Like all other properties for anything else. I beleive your way of putting data in Dicts is good for this. There should be master dict properties that keeps other dicts for each property object (form, control, lil builder....) So, at the end, for lets say Form, we have dict Form holding its properties. Manipulating values will be done via PGUI. |
This is actually alreday there. The dictionary Project() is the root/master. The current GRID() function stores the value in a static var to return it quickly. Of cause I can store it with the GUI() dictonary, but then it might be slower, and you had the concern that grid drawing should be fast. Storing the value in GUI() dictionary is a nice solution, though. When I find time, I'll test it.
| majkinetor wrote: | | Quote: | | But the problem is that they hide behind Tabs when created before the tab. |
Z-order of controls can be controled. I just faild to do so from AHK so far. Easy solution would be to delete and recreate statics on next selection (not move them) |
Will that be fast?
| majkinetor wrote: | | Quote: | | So I think we should discuss these designs first and then create the properties accordingly. |
This is bad way IMO. Properties GUI is object per se. It is entity on its own that can be added in any project and manipulated via its API as advanced control (like HiEdit for example). |
I don't argue the usefullness of the Property GUI. I just say that the basic design of LilBuilder has to be discussed and changed soon. As you say PGUI is an object that can be pluged in. But the design of LilBuilder and the fast speed its growing might keep us from using a different approach. I would like to find the best solution for window handling and selector handling first. Since these two are the very basics of the design. When we find a nice solution, all other things will fall in place.
| majkinetor wrote: | - I will see about multidock when I finish PGUI
- You can check out Owner
- Independant windows are the trivial solution
- SetParent doesn't destroy hwnd. U can use it normaly. |
First I want to get the Export/Import done, Rajat has done a great job, I just add special handlings.
_________________
Ciao
toralf  |
|
| Back to top |
|
|
Rajat
Joined: 28 Mar 2004
Posts: 1718
|
| Posted: Wed Jun 13, 2007 11:34 am Post subject: |
|
|
| toralf wrote: | | Maybe the inc\Menu.ahk should be moved to menu\ and renamed to Common.ahk to reflect its purpose? |
makes more sense... i looked only under the 'menu' folder.
| toralf wrote: | | Not intuitive enough I fear, but possible. I think hotkeys provide a faster access. |
i strongly feel this'd work out well. a text ctrl saying 'Grid' or 'Grid' size next to the arrow buttons can also be added.
| toralf wrote: | | But how to store the data and return it quikly? |
only the grid size in a number would be stored as a separate setting in gui settings in project file. would be loaded during import and saved during export. would be quick enough. your dicts are good for holding them during session.
| toralf wrote: | | I like extra toolbox and would love to keep that. At the end we do not need to create a maximized window. Making the toolbox a regular window and the other windows as owned will do the trick |
the toolbox would stay the same way, only a big gui background would be added. besides taking care of the existing problems, this'd also make the separate windows not look like orphans. it'd be more in line than an overhead. and Owner would solve the problems.
| toralf wrote: | | Could you please provide a list of controls with optimal H? E.g. |
checkbox and radio are bugs right now... i'd just make a small change. if H is not declared, make it 20 or 30 for these, at beginning of function.
_________________
 |
|
| Back to top |
|
|
toralf
Joined: 31 Jan 2005
Posts: 3841
Location: Bremen, Germany
|
| Posted: Wed Jun 13, 2007 12:45 pm Post subject: |
|
|
I just added these: | Quote: | - added grid size value per gui as gui prop "GridSize"
- changed Grid hotkeys to F6 and F7
- added menu items for toolbox to add a new or delete a gui
- removed ToolWindow option from toolbox
- changed made User guis owned by toolbox
|
Plus several more changes.
I hope this will solve all issues with grid and window handling, at least I like it. Please judge with next release (tonight, 7pm my time) :)
_________________
Ciao
toralf
Last edited by toralf on Wed Jun 13, 2007 12:50 pm; edited 1 time in total |
|
| Back to top |
|
|
toralf
Joined: 31 Jan 2005
Posts: 3841
Location: Bremen, Germany
|
| Posted: Wed Jun 13, 2007 12:49 pm Post subject: |
|
|
and this | Quote: | - default height for CheckBox, Radio control is now 23 pixel
|
I used the same hight as a button control. Thus 23 pixel. I hope that is ok.
_________________
Ciao
toralf |
|
| Back to top |
|
|
toralf
Joined: 31 Jan 2005
Posts: 3841
Location: Bremen, Germany
|
| Posted: Wed Jun 13, 2007 12:55 pm Post subject: |
|
|
When you are done, could you please post the code for the LilBuilder_Initialize() to use an INI file? Thanks.
_________________
Ciao
toralf |
|
| Back to top |
|
|
Rajat
Joined: 28 Mar 2004
Posts: 1718
|
| Posted: Wed Jun 13, 2007 12:56 pm Post subject: |
|
|
sounds good toralf, thanks!
for some strange reason i'd like the default control sizes to be in multiples of 5. more in line with grid if one decides to add it after adding a few controls.
_________________
|
|
| Back to top |
|
|
majkinetor
Joined: 24 May 2006
Posts: 3644
Location: Belgrade
|
| Posted: Wed Jun 13, 2007 1:00 pm Post subject: |
|
|
| Quote: | | Can you show me how? |
Yes I can
| Quote: | | Will that be fast? |
Probably fast enough. No way to tell until its implemented. I say lets forget about this for now. If I discover something good, I will post it here.
| Quote: | | I don't argue the usefullness of the Property GUI. I just say that the basic design of LilBuilder has to be discussed and changed soon. As you say PGUI is an object that can be pluged in. But the design of LilBuilder and the fast speed its growing might keep us from using a different approach. I would like to find the best solution for window handling and selector handling first. Since these two are the very basics of the design. When we find a nice solution, all other things will fall in place. |
Ok, Proeprties GUI is already there, you can test it any time. Its not fully finsihed but already usable and I will update it frequently until its perfect.
BTW, I think PGUI should be fundamental part of the LilBuilder as it makes anything possible to set via it - even shortcuts. The only thing to do before adding it to LilBuilder is to remove HLink control from the code as it unconditionaly puts WM_NOTIFY handler (that is, you can remove only its OnMessage). I will change its api to be on demand so both controls can coexist (HLink to be functional only in acctuall code). This will be solved when Chris implements dynamic function calls (I beleive this will happen soon)
| Quote: | | checkbox and radio are bugs right now |
And text.
_________________
|
|
| Back to top |
|
|
toralf
Joined: 31 Jan 2005
Posts: 3841
Location: Bremen, Germany
|
| Posted: Wed Jun 13, 2007 3:18 pm Post subject: |
|
|
@Majkinetor:
What message do I have to monitor to detect window minimize?
Edit: And Maximize?
_________________
Ciao
toralf |
|
| Back to top |
|
|
toralf
Joined: 31 Jan 2005
Posts: 3841
Location: Bremen, Germany
|
| Posted: Wed Jun 13, 2007 6:27 pm Post subject: |
|
|
New version 0.5.3 is out | Quote: | Rev 37
- fixed: toolbox now doesn't hide behind Traybar (thanks ahklerner, rajat, freakkk)
- changed initial gui size to w600 h450 to standard screen ratio 4:3
- enabled context menues for all controls
- added SysGet_GuiFrameSizes()
- removed SaveLoad_GetDiff()
- renamed GuiList to ListOfGuiID
- renamed SaveLoad_Export() to SaveLoad_ExportProject()
- fixed SaveLoad_ExportProject() in-ability to export tabs on tabs
+ added SaveLoad_ExportGui() and SaveLoad_ExportControl() to allow recursion
- changed properties that are for internal use only to start with a "_"
- enhanced control Prop "VarName"
- added special handling of statusbar and anchor to export
- changed Statusbar handling in gui, removed gui prop "StatusBarDeleted", but set the gui prop "_Statusbar" to negative HWND
- added grid size value per gui as gui prop "GridSize"
- changed Grid hotkeys to F6 and F7
- renamed Selector_DeleteControls() to Control_DeleteControlList()
- added menu items to toolbox to add a new or delete a gui
- added menu items to gui to delete the gui
- added Gui_Delete()
- removed ToolWindow option from toolbox
- changed made User guis owned by toolbox
- added gui prop "_FinalGuiID"
- added Gui_GetFreeUserGuiID()
- added Gui_IsGuiIDUnique()
- changed: menu item for anchor of control now shows the current setting
- fixed a bug in list of anchored controls
- default height for CheckBox, Text, Progress and Radio control is now 23 pixel (thanks Rajat and Majkinetor)
- changed default contents of some controls
- renamed SaveLoad_ReadProject() to SaveLoad_ImportProject()
- renamed SaveLoad_ReadGui() to SaveLoad_ImportGui()
- renamed SaveLoad_ReadControl() to SaveLoad_ImportControl()
- removed SaveLoad_ReadTabPage()
- removed SaveLoad_SetVarGlobal()
- added DropDownList control
- added message handler for WM_MOVING to clear selection and hide the selector (thanks Majkinetor)
- changed default Window title, it now always shows the GuiID and the Title
- moved some functions from inc\Menu.ahk into menu\CommonMenu.ahk
- renamed Menu_Anchor() to Control_Anchor()
- added gui prop "Label"
- added file inc\LB_IncludeFunctions.ahk for final script
Rev 38
- project file extention is set to ".lbp"
- LB function file extention for included functions is set to ".lbf"
- added control prop "_FinalVarName"
- added gridsize and resize handling for import
- !!! since project file format has changed, the included functions of the "final script" and the Stealer might not work yet
|
I guess now it could be bumped to 0.6, after some have tested the latest features. And also a new thread could be started. @Maj/Rajat: go ahead and create the accounts and thread.
_________________
Ciao
toralf |
|
| Back to top |
|
|
toralf
Joined: 31 Jan 2005
Posts: 3841
Location: Bremen, Germany
|
| Posted: Wed Jun 13, 2007 8:09 pm Post subject: |
|
|
Another update 0.6.0 | Quote: | Rev 39
- removed global vars <A_Gui>GuiWidth, <A_Gui>GuiHeight, Option, WorkArea<XXX>
- fixed included functions of the "final script"
Rev 40
- fixed Stealer
|
I adjusted the Stealer to the new project file format, I'm not sure if I messed up some features of it. Rajat, could you please tell me what I have done wrong?
@All: How can I detect by the gui Style if a gui is a toolwindow? Or is there a different possibility to find it out?
_________________
Ciao
toralf |
|
| Back to top |
|
|
Rajat
Joined: 28 Mar 2004
Posts: 1718
|
| Posted: Wed Jun 13, 2007 8:17 pm Post subject: |
|
|
| toralf wrote: | | @All: How can I detect by the gui Style if a gui is a toolwindow? Or is there a different possibility to find it out? |
ExStyle : 0x00000100 : normal window
ExStyle : 0x00000180 : toolwindow
by the way i hope its ok if i do the .ini workings tomorrow ... i'm busy with something.
_________________
|
|
| Back to top |
|
|
toralf
Joined: 31 Jan 2005
Posts: 3841
Location: Bremen, Germany
|
| Posted: Wed Jun 13, 2007 10:20 pm Post subject: |
|
|
Next new version 0.6.1
| Quote: | Rev 41
- Split off some changes into changes_prior_0.6.0.txt
- changed: Stealer should now detect toolwindows (thanks Rajat)
- added folder guis
- added "Set VarName", "Set Label", "Delete Content" and "Change Content" as common context menu items
- added control prop "Label"
- added control "Label" to export and import and final script
- created gui\ExportGui.xxx as a first try to create LilBuilders own guis with LilBuilder
- fixed bug in Import to apply ToolWindow/Resize
- enabled Run after Export again
|
_________________
Ciao
toralf |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Register
Profile
Log in to check your private messages
Log in
