in reply to Change readonly status of Win32::GUI::RichEdit

I know my comment is no usefull, but can't resist noticing that RichEdit is actually 'poor edit' compared to 'Text' widget of Tk
:)

Sorry

  • Comment on Re: Change readonly status of Win32::GUI::RichEdit

Replies are listed 'Best First'.
Re^2: Change readonly status of Win32::GUI::RichEdit
by ChrisR (Hermit) on Feb 11, 2005 at 20:38 UTC
    I'll agree with you on two things. You are correct in stating that your comment is not useful. I also agree that Tk's Text widget has a ton of options. However, I am not using Tk for this project. I have used Tk before and the Text widget. If I remember correctly, the Text widget has a readonly form called TextRO. Is that because the Text widget can't do this either? How do you go about changing the readonly status of the Text widget?
[reply]
      first, ROText is based on Text (i mean implementation, to check do some RTFS), this means that Text is able to become unresponsive to changes.

      Second, Text have -state disabled.

      what forces you using Win32::GUI?

[reply]
        ok. I don't want to get into a flame war here as this is not why I come to this site. I come here to give and receive useful information that helps in solving a stated problem or achieving a stated goal. That being said, I did make the mistake of calling ROText by TextRO. However, I do not want to disable the widget. I only want to make it readonly. Looking at the docs, I found nothing regarding readonly for Text. After RTFS for Text, I see the sub bindRdOnly but it is not documented or commented from what I can see and I would just be taking a stab in the dark at how to use it correctly.

        I am sorry if you are offended by my unfamiliarity/dislike of Tk since I see now that you are one of the maintainers on CPAN. I spent some time trying Tk and now I am spending some time using Win32::GUI. I found things I liked and disliked about Tk just as I am with Win32::GUI. At this point, I like Win32::GUI better, but I am just getting started. Next, I plan on trying out wxPerl. After a while, I'm sure I will be able to pick what I like best about each package and use them where they are best suited.

        I think the main point here is that I am using Win32::GUI and had a valid question about it. At least I thought it was a valid question. I have worked around the problem as I stated in an update to the original post even though it is not the way I would have liked to do it.

        Again, I don't come to perlmonks to flame or be flamed (even though it does happen sometimes). I come here because this is the best place I have found for perl questions and answers.
[reply]
[d/l]

In Section Seekers of Perl Wisdom