Sometimes we can tell what is going on by looking at the binary. But the
smallest bit of source that shows the problem is uusally the best. Like you
say, something very similar doesn't show the problem. The first thing that we
are going to do is to try to work out an app that shows the problem. If we
can't see it to start with, this is going to be hard, if you have something
similar that doesn't show it, it's going to be all the harder for us to
reproduce it. If we can't reproduce it, it's almost impossible to fix it. This
is probably not what you want to hear, but sometimes, reality sucks....
If I recall correctly, this has something to do with creating a dialog with a
NULL parent. Which as far as I'm concerned is way outside the scope of any docs
I've ever read. It sort of makes me think of the ethical concerns raised over
Dolly, the sheep......A widget with no parent, that just sort of appears......
On 10-May-00 at 18:11, Haral Tsitsivas ([EMAIL PROTECTED]) wrote:
> Rick Scott wrote:
>
> > Do things work as expected if you use XtSetSensitive instead of
> > SetValues?? XtSetSensitive does alot more under the hood than simply
> > setting the sensitive resource.
>
> This does not work either... Something else may also be causing
> this problem though!!! I commented all the lines that change
> focus sensitivity and the text fields are still not editable!
> Can you tell anything by looking at the symptom (by running the
> binary program) or do you need source to determine the problem.
> I don't know if I can duplicate the problem in a small example...
> I have another application very similar to this but it does not
> exhibit the problem!
>
> Thanks
>
>
> --
> --Haral Tsitsivas, UniSolutions Associates (http://www.unisol.com/)
> System Accounting & Chargeback, Backup and Restore, System Administration
> Voice: (949) 488-3960, Fax: (949) 443-5354, E-mail: [EMAIL PROTECTED]
>
>
