The problem with two threads was it didn't let me use MSG_GEN_ADD_CHILD from
the process thread, which was the original reason I moved the docgroup to
the UI thread a long time ago. Complains object block locked by wrong thread.
>3} After saying that you got it working by dropping to a single thread, you
>don't say whether your stack overflow problems have gone away running under
>Swat. If they have not gone away, you still have problems. Marcus' post
>holds true here.
Yeah, the stack problems are gone in the single threaded version.
>4) Monikers - As you noticed, the USE and REPLACE messages do different
>things with the monikers. Most often they are NOT interchangable.
I know that, but when I want to give it a text moniker from a string, I have
to use MSG_GEN_REPLACE_VIS_MONIKER_TEXT. Ready for this wierd thing? In the
code I showed to create an item and replace the moniker, it didn't work
until I told it to use a dummy moniker and then replaced it. (This problem
only came up when I went to one thread) But later on when I make another new
item, it lets me directly use replace.
>5) TimeLock - From your Swat trace it looks like your @callsuper() comes
>before your timelock code. Since the New/Open DBox is app modal, the system
>is probably keeping it on top until something is done with it. Try putting
>your timelock stuff before the @callsuper().
If I have a dialog pop up before the @callsuper in open_app, it never shows
up. What's happening is the timelock dialog shows up, and THEN the new/open
comes up above it.
------------------------------------------------------------------------
| I've always been afraid to die, but I think I'm more afraid to live. |
| -Billy Corgan, Smashing Pumpkins, The Aeroplane Flys High |
------------------------------------------------------------------------
| Edward Di Geronimo Jr. edwdig@bergen.org |
------------------------------------------------------------------------