On Apr 12, 2016, at 4:35 PM, Stephan Eggermont wrote:
>
> Yeah, this is just the first iteration.
> The field labels get used as ghost text now,
> conserving space. That is an easy change
> in the code generation.
Hi Stephan,
With the availability of Spec, this latest example, and your previous
Also, this default behavior can be reproduced with:
(LongMessageDialogWindow new entryText: 'Hello') open
(well, that doesn't set the title to "About"...)
I just can't figure out how to set the text for non-"long message" dialogs!
Take care,
Rob
>
>
>> On Apr 10, 2016, at 6:44 PM, B
Hello,
In Pharo 5.0 #50680
MessageDialogWindow new open
displays a message box with no text.
Should
(MessageDialogWindow new text: 'Hello') open
work?
I get a stack trace on CompositionScanner if I try to set the text.
Also, is there a way to display the dialog modally (re
Hi Bruce,
This is my first week in a LONG time too, so good luck!
If you open a Finder (Tools->Finder), and search for "about" (selectors), you
will find a bunch of things that respond to "aboutText", like "SystemWindow,"
and "ComposableModel."
The little drop-down arrow in the upper right of
nvisibility flag (v):
>
> GetFileInfo -a v /Applications
> # should echo 0 (invisibility flag not set)
>
> GetFileInfo -a v /bin
> # should echo 1
>
>
> On 9 April 2016 at 21:12, Robert J Rothwell <mailto:r.j.rothw...@gmail.com>> wrote:
> Hello,
>
&
Hello,
Is there a way to determine if a file is hidden? I couldn't find that in "Deep
into Pharo".
For example, I can get my desktop files with:
desktopFiles := FileLocator desktop children.
And now I would like to filter that collection to the non-hiddent files with
something like:
desktop
Thanks Johan, for your reply.
That's great that there is a path forward with Spec; I think I'll be able to
figure it out!
I'll have to dig deeper into updateList, because right now the only thing it
seems to do for me is clear any list selections, so I'm not sure if there is
supposed to be a r
Thanks Stephan, this is a very nice example of lots of Spec usage that I'm sure
I can learn a lot from!
As far as refreshing the list view, you did the same thing that I found to work
by using the ListModel>>items: message, which in your case was very natural
because you are creating a new, fil
