> >When I try to use the helptext: to set a tooltip on toolbar items or
> >even regular buttons, I get nothing. Do I need to do something more to > >make it work? > > Currently, in Pollock, the helpText isn't hooked up to anything. It awaits tools > to activate. What do you mean when you say that it awaits tools to activate? -Carl Gundel, author of Liberty BASIC http://www.libertybasic.com |
Carl,
> What do you mean when you say that it awaits tools to activate? There is no fly by help mechanism in Pollock as yet. Tools will add that in the future. Getting and setting of the text is all that Pollock itself supports. And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? |
I kind of see Carl's point though, what is so inherently special about hover
help that makes it part of tools? I would have thought that buttons and scrollbars responding to mouse clicks is not unlike all widgets responding to mouse hovers? Cheers! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 [hidden email] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. -----Original Message----- From: Samuel S. Shuster [mailto:[hidden email]] Sent: Tuesday, July 18, 2006 3:52 PM To: Carl Gundel Cc: 'Vwnc' Subject: Re: [7.4][Pollock]Helptext not working Carl, > What do you mean when you say that it awaits tools to activate? There is no fly by help mechanism in Pollock as yet. Tools will add that in the future. Getting and setting of the text is all that Pollock itself supports. And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? smime.p7s (4K) Download Attachment |
In reply to this post by Carl Gundel
> From: "Boris Popov" <[hidden email]>
> I kind of see Carl's point though, what is so inherently special about hover > help that makes it part of tools? I would have thought that buttons and > scrollbars responding to mouse clicks is not unlike all widgets responding > to mouse hovers? I wasn't trying to make that point, but you did rather well. I don't understand why this isn't in there already. Perhaps Vassili likes this particular piece of work and asked Sam if he could tackle it? ;-) -Carl Gundel, author of Liberty BASIC http://www.libertybasic.com |
Carl,
> I wasn't trying to make that point, but you did rather well. I don't > understand why this isn't in there already. Perhaps Vassili likes > this > particular piece of work and asked Sam if he could tackle it? ;-) More like Vassili has a Generic State Transition Framework as well as a prototype, that will be released as a tool along with Splash. And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? |
In reply to this post by Martin McClure
Just a quick update on the progress. It seems that the bug was located
and squashed, it will however require a new VM build. The conclusion is that it likely affects all Unix VMs, not just Linux. It's not clear to me yet if this will be deemed enough to trigger a release of an official bug fix VM at this point. It should make the 7.5 VMs at the latest though. Thanks to all for helping out with this. Martin Martin McClure wrote: > Martin Kobetic wrote: > >> I can reproduce it on a Fedora Core 4 (64bit but running the 32-bit >> VM). I note that it doesn't run hot when connected to a local >> repository (on the same host) but does when connecting to any remote one. >> >> I've created AR#50994: "A remote Postgres connection makes the Linux >> VM run hot" for this issue. Thanks to all who reported the problem. > > > Thanks for the AR! > > -Martin > |
Martin Kobetic wrote:
> Just a quick update on the progress. It seems that the bug was located > and squashed, it will however require a new VM build. The conclusion is > that it likely affects all Unix VMs, not just Linux. It's not clear to > me yet if this will be deemed enough to trigger a release of an official > bug fix VM at this point. It should make the 7.5 VMs at the latest though. Thanks for the update. I don't know how much making an official bug fix VM costs you in time, but I tend to vote for releasing a fix sooner rather than later. In a development environment this is just an annoyance, but a significant annoyance -- I sit there connecting and disconnecting from Store until I finally get a connection that doesn't hog my CPU. However, in a production situation consuming a CPU per VM would just not be acceptable, so I could not recommend using this VM version in most production situations. Regards, -Martin |
How can I open an instance of DialogWindow that doesn't cause VisualWorks to
lock until the window is closed? I tried the most obvious idea of having a custom openNonBlocking method that calls super open. Didn't seem to make any difference. :-( Thanks, -Carl Gundel, author of Liberty BASIC http://www.libertybasic.com |
In reply to this post by Martin McClure
I should make clear that this was a very early update. There were no
discussions or decisions about a bug fix VM yet, so don't take my note as a sign of it coming or not. I just wanted to provide a bit of early feedback. Nevertheless I will forward your comment to the relevant parties. Thanks, Martin Martin McClure wrote: >>Just a quick update on the progress. It seems that the bug was located >>and squashed, it will however require a new VM build. The conclusion is >>that it likely affects all Unix VMs, not just Linux. It's not clear to >>me yet if this will be deemed enough to trigger a release of an official >>bug fix VM at this point. It should make the 7.5 VMs at the latest though. > > > Thanks for the update. > > I don't know how much making an official bug fix VM costs you in time, > but I tend to vote for releasing a fix sooner rather than later. In a > development environment this is just an annoyance, but a significant > annoyance -- I sit there connecting and disconnecting from Store until I > finally get a connection that doesn't hog my CPU. > > However, in a production situation consuming a CPU per VM would just not > be acceptable, so I could not recommend using this VM version in most > production situations. > > Regards, > > -Martin > > |
In reply to this post by Carl Gundel
Look at DialogWindow>>windowType.
Additional locking is done by grabing the mouse. See DialogWindow>>open. HTH, Christian > Von: Carl Gundel > > How can I open an instance of DialogWindow that doesn't cause > VisualWorks to > lock until the window is closed? I tried the most obvious > idea of having a > custom openNonBlocking method that calls super open. Didn't > seem to make > any difference. :-( > > Thanks, > > -Carl Gundel, author of Liberty BASIC > http://www.libertybasic.com > > > > |
Carl
There are two parts to dialog locking, one part is as Christian said, mouse grabbing in the image. The other part is done by the VM, or the OS, and is specified by the window type. If you look at the debugger you will notice that when it grabs control and a dialog was open it changes the window type of the window as well as releasing mouse grabs. You can kind of simulate dialogs by using a combination of mouse grabs and insuring the window stays on top by reraising it if it gets covered. I recall someone writing about using this technique a few months ago. Terry =========================================================== Terry Raymond Smalltalk Professional Debug Package Crafted Smalltalk 80 Lazywood Ln. Tiverton, RI 02878 (401) 624-4517 [hidden email] <http://www.craftedsmalltalk.com> =========================================================== > -----Original Message----- > From: Christian Haider [mailto:[hidden email]] > Sent: Wednesday, July 26, 2006 2:45 PM > To: 'Carl Gundel'; 'vwnc-list' > Subject: AW: [7.4][Pollock]DialogWindow question > > Look at DialogWindow>>windowType. > Additional locking is done by grabing the mouse. See DialogWindow>>open. > > HTH, Christian > > > Von: Carl Gundel > > > > How can I open an instance of DialogWindow that doesn't cause > > VisualWorks to > > lock until the window is closed? I tried the most obvious > > idea of having a > > custom openNonBlocking method that calls super open. Didn't > > seem to make > > any difference. :-( > > > > Thanks, > > > > -Carl Gundel, author of Liberty BASIC > > http://www.libertybasic.com > > > > > > > > |
Free forum by Nabble | Edit this page |