HMGforum.com

I had started working on RadioGroup.

I have uploaded a basic model of RadioGroup. I am struck in the 'options' method. All the options are shown in a single line. I had done as suggested by the QT Docs. Somebody, please help me out.

You can please run the demo_3 in \svn\samples\radiogroup folder.

rathinagiri wrote:I always document the missing properties/events/methods I work on a control in TODO.TXT already.

I hardly make any EXTENSIONS to the controls as I rush to implement new controls.

This was my idea too, but, when researching I'm finding wonderful stuff that can be implemented easily (take a look at new tab control demos).

Moreover, some extensions are 'automatically' in place, since they are inherited from control class. We should document those too.

Martin,

Los ejemplos de Progressbar no pueden compilarse.

The Progressbar samples can't be compiled.

Roberto Lopez wrote:Martin,

Los ejemplos de Progressbar no pueden compilarse.

The Progressbar samples can't be compiled.

I've fixed and commit the changes.
You had an outdated build.bat file.

rathinagiri wrote:I had started working on RadioGroup.

I have uploaded a basic model of RadioGroup. I am struck in the 'options' method. All the options are shown in a single line. I had done as suggested by the QT Docs. Somebody, please help me out.

You can please run the demo_3 in \svn\samples\radiogroup folder.

I've was about an entire week fighting against main menu because the persistence and scoping thing.

According demoqt and guidance that Pritpal got me, I've learned the following:

If an object variable is gone, the QT widget that it holds, will be gone too.

This is the reason because in demo QT there are objects returned as array elements that are never really used. That is done to keep the object 'alive'.

I'm not fully sure, but the problem with radiogroup appears to be the oLayout variable.

If you look at the mainmenu, menupopup, menuitem, tab, tabpage, toolbar and toolbutton classes, you'll see some 'nice' tricks that I've found to overcome this HBQT behavior.

Roberto Lopez wrote: If you look at the mainmenu, menupopup, menuitem, tab, tabpage, toolbar and toolbutton classes, you'll see some 'nice' tricks that I've found to overcome this HBQT behavior.

Perhaps, the best way will be to create a DATA in the radiogroup class to hold layout object.

Roberto Lopez wrote:

Roberto Lopez wrote: If you look at the mainmenu, menupopup, menuitem, tab, tabpage, toolbar and toolbutton classes, you'll see some 'nice' tricks that I've found to overcome this HBQT behavior.

Perhaps, the best way will be to create a DATA in the radiogroup class to hold layout object.

I've fixed and committed the changes.

Thanks Roberto. I too have thought the same. I had accidentally done that in Grid control to hold the oHeaderViewObject for effecting the on headclick event. I thought it could be of solving the scoping problem you mentioned.

But didn't try on radiogroup. Thanks for pointing out.

Hello,

Till now I cannot solve inputmask problem of textbox control fully. Inputmask (especially for numeric data types) is behaving differently. I can't solve the decimal point problem.

Please help me.

I am now searching for validator

Not sure where to put