Paul Ishenin schrieb:
30.03.12 5:24, Hans-Peter Diettrich wrote:
So what should happen in such a case, where the developer didn't observe
the rules? Should it be considered a fatal bug, and raise an exception?
It is a normal situation when something is docked and have DragKind
dkDock even
Paul Ishenin schrieb:
28.03.12 23:23, Hans-Peter Diettrich wrote:
Currently dragging is broken in the LCL, see Mantis #18525. Currently
any attempt to undock a docked window makes at least a Windows
application hang, in an unusable state, until a *different* application
is activated by the
Paul Ishenin schrieb:
29.03.2012 6:14, Paul Ishenin wrote:
28.03.12 23:23, Hans-Peter Diettrich wrote:
Currently dragging is broken in the LCL, see Mantis #18525. Currently
any attempt to undock a docked window makes at least a Windows
application hang, in an unusable state, until a
29.03.2012 15:26, Hans-Peter Diettrich wrote:
2) The example is too simple, it also works with a different DockManager.
Try again with a reasonable example, where the misbehaviour can be
observed, e.g. with the IDE.
I believe you that IDE docking may behave wrong but why you put the
29.03.2012 14:52, Hans-Peter Diettrich wrote:
The current situation, and your arguments, read to the user like:
We know that there exist bugs, and we know how to eliminate fatal
consequences, but we prefer to leave our code in unusable state.
This is how you see it. Read it so:
We know that
Paul Ishenin schrieb:
29.03.2012 15:26, Hans-Peter Diettrich wrote:
2) The example is too simple, it also works with a different DockManager.
Try again with a reasonable example, where the misbehaviour can be
observed, e.g. with the IDE.
I believe you that IDE docking may behave wrong but
Paul Ishenin schrieb:
29.03.2012 14:52, Hans-Peter Diettrich wrote:
The current situation, and your arguments, read to the user like:
We know that there exist bugs, and we know how to eliminate fatal
consequences, but we prefer to leave our code in unusable state.
This is how you see it.
29.03.12 20:30, Hans-Peter Diettrich wrote:
Some bugs cannot be fixed in code. E.g. when a form or control is
docked in code, what should happen to its DragKind? When the DragManager
requires a properly initialized DragKind, in order to start the proper
operation, should the property of the
Paul Ishenin schrieb:
29.03.12 20:30, Hans-Peter Diettrich wrote:
Some bugs cannot be fixed in code. E.g. when a form or control is
docked in code, what should happen to its DragKind? When the DragManager
requires a properly initialized DragKind, in order to start the proper
operation, should
30.03.12 5:24, Hans-Peter Diettrich wrote:
So what should happen in such a case, where the developer didn't observe
the rules? Should it be considered a fatal bug, and raise an exception?
It is a normal situation when something is docked and have DragKind
dkDock even I have no chance do
Currently dragging is broken in the LCL, see Mantis #18525. Currently
any attempt to undock a docked window makes at least a Windows
application hang, in an unusable state, until a *different* application
is activated by the user.
I see no reason why the submitted patch should not be applied,
28.03.12 23:23, Hans-Peter Diettrich wrote:
Currently dragging is broken in the LCL, see Mantis #18525. Currently
any attempt to undock a docked window makes at least a Windows
application hang, in an unusable state, until a *different* application
is activated by the user.
I see no reason why
29.03.2012 6:14, Paul Ishenin wrote:
28.03.12 23:23, Hans-Peter Diettrich wrote:
Currently dragging is broken in the LCL, see Mantis #18525. Currently
any attempt to undock a docked window makes at least a Windows
application hang, in an unusable state, until a *different* application
is
13 matches
Mail list logo
