HMGforum.com

2010-10-29 15:58:00 UTC-0300 Roberto Lopez (<mail.box.hmg@gmail.com>)
* hmgide/ide.prg
* Changed cursor in form editor.

2010-10-29 16:55:00 UTC-0300 Roberto Lopez (<mail.box.hmg@gmail.com>)
* hmgide/ide.prg
! Little bug fixed and some minor changes.

2010-10-29 17:30:00 UTC-0300 Roberto Lopez (<mail.box.hmg@gmail.com>)
* hmgide/ide.prg
! Various minor bugs fixed on form editor.

rathinagiri wrote:I can't run samples/window.main/demo_3.prg. Following is the error_log. What is happening?

Called from __HBQT_ERROR( 0 )
Called from QMAINWINDOW:CONNECT( 0 )
Called from WINDOW:ONSTATECHANGE( 1117 )
Called from WINDOW:_ONMAXIMIZE( 1079 )
Called from WINDOW:ACTIVATE( 1777 )
Called from MAIN( 176 )

As I said, there were changes in the connect/signal/slots area and hmg bulndled with hmg is taken in the middle of the changes. Infact demo_3 works with later versions of harbour.

It seems to be related on duplicate :connect, or better said, the error seems reported due during the try to connect an event that was already connected.

In window.prg, line 1116 you should have a remmed :disconnect. Please remove the rem and recompile hmg. Now it should work.

Please read my next message

TO all hmg developers.

I want to inform you that signal/slot subsystem underwent some changes in how they report success/failure.

We should always check :connect return value.

A .T. means the connect went OK
A .F. means the connect failed: if you were connecting an event, .F. means that the same event is already connected: the system doesn't apply new setting but maintains the old. If you were connecting a signal, .F. means that Qt, after all the checks done on parameters, failed to do the connection.
In all other cases (non existant signal, wrong parameter types, etc) it will throw an RTE with a number. Each kind of error has a id value that is added to 1200. Duplicate event error was -3 and infact rathinagiri had a error number 1197 on screen... Now, as I said, -3 return .F. and not RTE.

In the last harbour, it is now safe (it returns .F.) to call :disconnect() on a not-connected event. It is better to reinstate the :disconnect before the :connect in hmg code...

Thanks a lot Francesco.

Thanks Francesco.

I'll update the binaries soon. Then we'll do the required changes.

Roberto Lopez wrote:Thanks Francesco.

I'll update the binaries soon. Then we'll do the required changes.

Ok, so will be aligned for a while and I may commit some changes I have for hmg....

Roberto Lopez wrote: Well... it is regarding IDE form editor.

We are using this code to handle controls moving:

Code: Select all

	&cVar:oQTObject:connect( QEvent_MouseMove, {|p| ProcessControlDrag( p , oControl ) } )
	&cVar:oQTObject:connect( QEvent_MouseButtonPress, {|p| ProcessControlMousePress( p , oControl ) } )
	&cVar:oQTObject:connect( QEvent_MouseButtonRelease, {|p| ProcessControlMouseRelease( p , oControl ) } )

This works for most controls, but this is not working for some others, ie: QListBox, QTableWidget and QTableView.

So, we are looking for alternate solutions for those controls.

I have some ideas:
- try to set the object inactive
- use a placeholder object, for example a image of the object... if you have a look, in qt creator they just put the box on the form, not the content....

mmmmm..... do you return .T. from th ProcessControl* functions ????

2010-10-30 10:48:00 UTC-0300 Roberto Lopez (<mail.box.hmg@gmail.com>)
* hmgide/ide.prg
* Some work on form editor (selecting a control, updates objectlist combo).