Pharo 6.0
Latest update: #60410 Hi Several points that we MUST improve - I often get an error when I save code. SubscriptOutOfBounds: 0 extent ^ self actualWidth ifNil: [ self minimumExtent ] ifNotNil: [ (self actualWidth + self margins left + self margins right) @ (self lines last bottom - self lines first top + self margins top + self margins bottom) ] In RubParagraph apparentl self lines last... tries to access the 0 indexed element :( - How do we get the old textual stack description? Now I wanted to report it and share with you the stack..... oh boy! I thought it was file out but no it just save one method definition (So great) I got Fuelout the stack in the menu but this is not what I want. :((((((((((((((((((((((((((((((( - Finally BTW I clicked on report and I have no idea what it does not mean. The fly by help is empty :((((( So like an idiot I did a screen capture. This broke totally my feel. In less than 10 min I left like either the system became less good or I'm totally stupid. Stef Screen Shot 2017-02-23 at 22.50.52.png (351K) Download Attachment |
On Thu, Feb 23, 2017 at 10:55 PM, stepharong <[hidden email]> wrote: Pharo 6.0 In the toolbar menu of the stack you find 'Fuel out stack' and 'Copy to clipboard'. 'Copy to clipboard' copies a textual description of the stack that can then be pasted in an email. Is this the "old textual description" or are you referring to something else?
What action did you use to file our the textual description? Cheers, Andrei
|
On Fri, 24 Feb 2017 00:05:10 +0100, Andrei Chis <[hidden email]> wrote:
Ok this is what I was looking for. It looks like a generic copy past entry so I did not tried it. Can you rename it into copy textual stack? Then I do not get why we could not get action about the current context and action about the complete stack together. Because these are not method that we see but contexts.
fileout in the main menu when you clik on the stack element. I never ever used it since 2006.
do you have an idea about what is this Send a report: it looks totally obscure and useless.
-- Using Opera's mail client: http://www.opera.com/mail/ |
On 24/02/2017 08:44, stepharong wrote:
> Then I do not get why we could not get action about the current context > and action about the complete stack together. > Because these are not method that we see but contexts. > > +1000 I opened an issue about that in Pharo 5 after the integration of the GTDebugger but it got closed since apparently nobody else cared. To have two menu with one having only two actions we don't use often is almost the same as have only one menu because nobody will look for the second. -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France signature.asc (817 bytes) Download Attachment |
In reply to this post by stepharong
On Fri, Feb 24, 2017 at 8:44 AM, stepharong <[hidden email]> wrote:
Indeed the name is confusing (even if it's always been like that). I renamed it yesterday to 'Copy Stack to Clipboard'. Is that better? (It fits also with 'Fuel out Stack') Cheers, Andrei
|
thanks Yes it will be much better. Stef On Fri, 24 Feb 2017 10:39:51 +0100, Andrei Chis <[hidden email]> wrote:
-- Using Opera's mail client: http://www.opera.com/mail/ |
Free forum by Nabble | Edit this page |