Re: [Boa Constr] Boa CVS tutorial

[Riaan B. <riaan@e.co.za>]

Hi Patrick,

"Patrick K. O'Brien" wrote:
> 
> Thank you. That was the boost I needed to get me over the CVS hump. Now that
> I have the command line cvs working, I have some questions about boa because
> I still can't quite get it to work:
> 
> I did a brand new checkout of boa (from a dos prompt using the command line
> cvs) 

Which you could also have done from within Boa ;)

> and then opened boa and some of the boa source files are immediately
> displaying in the CVS folder with a red icon. What is that all about?

Means exactly the same as WinCVS, red means the file have a 
modification date bigger than their checkout date. In other words
modified after checkout.

I don't know why they would be modified, but doing a update will fix
the filedate if that is the only difference.

> 
> When I select one of the files in the CVS folder, right click and select
> Update or Status or Diff, I get a Debug dialog box (which gets hidden by the
> editor window) that says
> 
> ..\msw\app.cpp(1302): assert failed: wxYield called recursively
> Do you want to stop the program?
> You can also choose [Cancel] to suppress further warnings.
> 
> I select the No button and then get the CVS command line dialog which does
> its thing and closes so fast that I can't tell what it did, or didn't, do.
> Except that I would expect to see some results from status or diff and I
> don't in boa while I do from the dos prompt. I actually think I get the
> results in boa but the dialog closes immediately after it gets a response
> back from the repository so I don't have time to see the result.

Your next mail message is the real clue. It seems that I may not call 
wxYield() from within a popup menu event call :(

I have found no workarounds, as I really want to call wxYield() 
where I do. Best advice for now, choose [Cancel] to supress further
warnings.

I do not use the HYBRID version as Boa runs VERY SLOW under the HYBRID
version. Also under HYBRID when Boa is run in Boa, it does not close
properly. 
Calling wxYield() in a menu event has no ill effects under the normal 
version as far as I can see.

The warning dialog (or wxYield :/) also seems to interfere with the 
dialogs after it, so it works without the warnings.
The only time there will be no response fram the server is for example
if you do a diff and there are no differences.

> 
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net