This does not fix the issue. The only thing that works for me is making
sure I double-click whenever I am done with the edit tool. If I switch
to a different tool before double-clicking, the memory issue occurs. If
I close the dialog with StopAllTools(), the memory issue occurs.
On 11/9/2016 11:53 AM, klaas.holwerda wrote:
How about StopAllTools(), just do a search on the code, I think it is
clear how to use it.
But a2dStToolContr does the same at destruction??
I do remember this in an application as being the same problem, and
the solution was StopAllTools.
Klaas
On 11/08/2016 11:45 PM, Mike Gibson wrote:
So I've further tracked down what may be causing this issue. If the
user selects "edit" (which uses an a2dRecursiveEditTool), the problem
does not appear to occur if the user double-clicks to end the tool
before closing the dialog box.
However, I cannot expect the user to remember to do this. If the user
leaves the edit tool open, I need to close the edit tool to prevent
issues. However, I have not discovered the correct way to do this. I
have tried to call StopTool() on the a2dRecursiveEditTool on
destruction, but it does not solve the problem in every case.
Is there a way to go through an a2dStToolContr class on destruction,
and make sure that every tool is popped from the stack and deactivated?
- Mike
On 11/5/2016 12:04 PM, klaas.holwerda wrote:
On 11/04/2016 11:03 PM, Mike Gibson wrote:
I switched back to a normal a2dDrawing. After editing, I close the
dialog. When I reopen and try to edit, I get this error:
Editing what with a dialog?
Are do you mean the canvas as part of a dialog?
I don't know what you do and how you do it.
You can send me a stack when this happens? And what is the object
(obj) in question?
If you can reproduce it in a sample, I can check what is going on,
but with just this I don't know.
Regards,
Klaas
I also get odd behavior like malfunctioning controls in the UI as
if there is some underlying memory issue.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
Wxart2d-users_dev mailing list
Wxart2d-users_dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
Wxart2d-users_dev mailing list
Wxart2d-users_dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Wxart2d-users_dev mailing list
Wxart2d-users_dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Wxart2d-users_dev mailing list
Wxart2d-users_dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
