Et voilà, I just opened the issue, the number given by fogbugz is 17951.
Thanks again - Carlos
On Thu, Apr 7, 2016 at 1:13 PM, Carlos Lombardi
wrote:
> Hi Stephan,
>
> thank you for your prompt answer.
>
> We are actually using TextEditor>>changeTextFont, which initiates the
> following message
Hi Stephan,
thank you for your prompt answer.
We are actually using TextEditor>>changeTextFont, which initiates the
following message call chain
TextEditor>>changeTextFont
StrikeFont class>>fromUser:
MorphicUIManager>>fontFromUser:
StrikeFont class>>fromUser:allowKeyboard:
Theref
On 06-04-16 15:27, p...@highoctane.be wrote:
Is there anything else than a SmalltalkEditor there? Now there is Rubric
too, but...
The superclass of SmalltalkEditor is TextEditor. That is the one I'd expect.
Stephan
Stephan,
Is there anything else than a SmalltalkEditor there? Now there is Rubric
too, but...
Phil
On Wed, Apr 6, 2016 at 2:34 PM, Stephan Eggermont wrote:
> On 05-04-16 23:22, Carlos Lombardi wrote:
>
>> We had another problem to obtain a mix-style PluggableTextMorph. When the
>> Text is acce
On 05-04-16 23:22, Carlos Lombardi wrote:
We had another problem to obtain a mix-style PluggableTextMorph. When the
Text is accepted, the model is given actually a style-less Text, this is
explicitly established in PluggableTextMorph>>acceptTextInModel. I guess
that such is convenient when the Te
On 05-04-16 23:22, Carlos Lombardi wrote:
I provisionally patched this issue by modifying the class method in
StrikeFont, in order to give the menu Strings instead of Associations. As
far as this way of selecting a point size is still usable, it would be nice
to have this issue fixed. If there is
Hi,
proviso:
this is my first mail to a Pharo list. I guess that it is pertinent for the
pharo-dev list, since it describes a possible failure in Pharo 4 and an
enhancement suggestion. If this mail is better suited for the pharo-users
list, or else it should be better addressed to both lists, plea
