Re: Re: Some problems in the migration from Classic to Phoenix (cry for help?)

Robin Dunn <[email protected]> Mon, 16 Jul 2018 16:20:51 -0700 (PDT)
Newsgroups gmane.comp.python.wxpython.devel
Message-ID <[email protected]>
Is it possible that there is a timer that has been destroyed while there 
was still a timer event pending? Maybe if you explicitly call each timer's 
Stop() method when you are done with them (or when the window they are 
associated with is being closed.)


--
Robin


On Wednesday, July 11, 2018 at 1:01:53 PM UTC-7, Hélio Guilherme wrote:
>
>
> Here it is the stacktrace.
>
> Thanks.
>
> quarta-feira, 11 de Julho de 2018 às 01:47:01 UTC+1, Scott Talbert 
> escreveu:
>>
>> Do you mind sharing the stacktrace anyway? 
>>
>> On Tue, 10 Jul 2018, Hélio Guilherme wrote: 
>>
>> > 
>> > Hi again, 
>> > 
>> > I am still desperate with the crashing bug (I wish it would be smashing 
>> :) 
>> > ). It happens on Linux, Windows and MacOS with wxPython >=3.0.3  (not 
>> with 
>> > 2.8.12.1). 
>> > 
>> > If anyone can spare time and knowledge to help me debug this, it would 
>> be 
>> > wonderful for the Testers Community to have a Python 3 Robot Framework 
>> IDE 
>> > (RIDE). 
>> > 
>> > I can get the stack trace (but it does no tell me anything :(). 
>> > 
>> > Attached is RIDE and Inspection Tool screenshot. I ask if that would be 
>> a 
>> > "normal" application configuration? 
>> > 
>> > I can produce the crash by double-clicking the "For Loop Keyword" cell 
>> > (which would "jump" to its definition). Also attach the text file. 
>> > 
>> > I have no other way to create a minimal demonstrating app. 
>> > 
>> > Current code is at 
>> https://github.com/HelioGuilherme66/RIDE/tree/gificons 
>> > To call from cloned repository, use: 
>> > invoke devel -a --debugconsole 
>> > 
>> > To call from installed, use: 
>> > ride.py --debugconsole 
>> > 
>> > Thank you, 
>> > Hélio 
>> > 
>> > quarta-feira, 7 de Fevereiro de 2018 às 23:26:13 UTC, Hélio Guilherme 
>> > escreveu: 
>> >       Hi all, 
>> > 
>> >       I announced already on this list that I am migrating an 
>> >       application from wxPython 2.8.12.1 to Phoenix, and at the same 
>> >       time from Python 2.7 to Python 3.6. 
>> > 
>> >       Well, I have a lot of software design problems, that I slowly 
>> >       try to solve, but the immediate things are some bugs that I 
>> >       blame on Phoenix side. Although, they may be because the code 
>> >       was done to Classic and there may be some unnoticed differences 
>> >       in Phoenix which have impact. 
>> > 
>> >       List of issues: 
>> >       - On Windows 10, wxPython 4.0.0, python 2.7.13: 
>> >           The selection of text on a CustomGrid cell, is not 
>> >       highlighted.  (this problem existed once in Linux, GTK3+ but was 
>> >       fixed, and at the moment it was OK on Windows) It is OK on 
>> >       Windows 7. 
>> >       - On Windows 7 and 10, wxPython 4.0.0/4.0.1, python 2.7.13: 
>> >            It is not possible to type text on certain fields, like, 
>> >       Library button and Name field. The only way is to paste with 
>> >       context menu (CTRL-V also not working). No problems with GTK3+. 
>> >            On certain text fields like Add Scalar button, Name text 
>> >       field, there is no blinking cursor. No problems with GTK3+. 
>> >            It does not work detaching a floating tooltip window with 
>> >       double-click, this works fine with 2.8.12.1 (on Cell Editor, 
>> >       type Log and press CTRL-M or CTRL-SPACE). No problems with GTK3+ 
>> > 
>> >       Finally on all platforms: 
>> >            - When we move from the flat notebook tabs to the Editor 
>> >       (Grid), it may render grayed color without cells (there is a 
>> >       workaround, to move to Text Editor and back). 
>> >            - When we navigate from Editor to project Tree, we get 
>> >       crashes (not always). 
>> >       I suspect that these are related on how it was designed. The 
>> >       Editor is being Created when we select its Tab and probably 
>> >       Destroyed when replaced. 
>> > 
>> > 
>> >       If by chance anyone would like to install and try this Robot 
>> >       Framework IDE, I have a release here (there is also a link to a 
>> >       Wiki page with the known Issues). 
>> >       One day when my project is bug "free", I'll start doing 
>> >       regression tests for all the Demos of wxPython ;). 
>> > 
>> >       pip install wxPython 
>> >       pip install robotframework 
>> >       pip install pygments 
>> >       pip install 
>> >       https://github.com/HelioGuilherme66/RIDE/archive/v1.7.2.zip 
>> > 
>> >       Thank you for your time. I am also grateful to all the 
>> >       opensource developers that makes all this possible (specifically 
>> >       GTK, wxWidgets, wxPython and robotframework/RIDE). 
>> > 
>> >       Hélio 
>> > 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> Groups 
>> > "wxPython-dev" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an 
>> > email to [email protected]. 
>> > For more options, visit https://groups.google.com/d/optout. 
>> > 
>> >
>
>

-- 
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.