Hi,
A while ago, Stef reported that he could not select text anymore in the new
Rubric-based interfaces (inspector, playground).
I noticed this as well but only occasionally. Here is what I found.
TextMorph uses a kind of a simulation to support smart selection. As a
result, you basically can do:
- click once at the beginning of a parenthesis
- wait a couple of seconds
- click again
==> and the text is selected
Instead of this mechanism, Rubric relies on real double click events. So,
in order to select something you have to click-click quickly.
Now, the issue is that every once in a while, somehow the image seems to
stop receiving double clicks. I experienced this both on Windows and on
Mac. As a consequence, it appears that you cannot select anymore with
double click. To double check that this happens, you can try double
clicking on the window title and you will see that it does not maximize
anymore.
If you close the image and open it again, the problem gets fixed. This
makes it difficult to reproduce and debug.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I am preparing a talk on software environmentalism (
http://www.tudorgirba.com/blog/keynote-at-ecoop-2014) and I am looking for
resources around the following issues:
- the amount of source code in the world
- the amount of time spent on reading code
- the development tools in use
- how people use custom tools (for example, unix/linux scripts)
- or other similar ones
Do you happen to know any pointers that go in this direction?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hello everyone,
In a former moose version, it was being able to do on a MooseGroup : Browse>>In Eye See Editor.
Now it is not possible...
What tool should I use to draw graphs?
Thanks in advance
Cheers,
Vincent BLONDEAU
________________________________
Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1079 by v.blonde...(a)gmail.com: , (comma) should not be
implemented in the FM*MultivalueLink classes
http://code.google.com/p/moose-technology/issues/detail?id=1079
Describe the problem: what do you get? what do you expect?
When you send the message "," to a FM*MultivalueLink, you expect to have a
copy of your collection with no impact on the old one.
But it's not the case with the FM*MultivalueLink instances which are
keeping a link to the old collection...
I propose to implement "," in FM*MultivalueLink by:
self shouldNotImplement
What do you think ?
How to reproduce the problem: step by step if necessary
Execute:
|class|
class:=FAMIXClass new addAttribute:(FAMIXAttribute new);yourself.
class methods
Here "class methods" is empty
class methods , class attributes.
class methods
Here "class methods" is not empty !
Additional information: platform, context which may impact the problem
W7 - Moose latest
Please fill in the labels with the following information:
* Type-Enhancement
* Component-Fame
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings