Jump to content
You must now use your email address to sign in [click for more info] ×

00Ghz

Members
  • Posts

    658
  • Joined

  • Last visited

Posts posted by 00Ghz

  1. What have you all been smoking???  :ph34r:

    No smoking here good sir!!!!

     

    We are experiencing the first symptoms of a contagious and dangerous condition called “New Release Withdrawal Syndrome”.

     

    Stage 1: Involves OCD about asking of a release date. The addiction must be fed of course.

    Stage 2: The patients start talking about code and various algorithms in order to draw attention of the ones who feed them with the “good stuff”. The AD forum slowly transforms into StackExchange. 

    Stage 3: This stage is filled with schizophrenic dreams about new features, psychopathy and social reclusion, while at the same time being consumed by keyboard finger convulsions of writing posts, and other SJW behaviour.

    The final part involves the patient developing resistance to this condition by writing their own design software with a release schedule of Friday, every week. As such the flow of spice is reestablished and things go back to normal.

     

    Cheers ;)

  2. Just to expand on the above, the variable releaseDate_ETA is initialized to the value math.random(), and in the while loop the variable releaseDate is set to math.random() + 1, so the actual release date is always going to be greater than the ETA and therefore the condition if releaseDate == releaseDate_ETA will never be satisfied.

    But as far as I am aware math.random() generates a random value for every call of said function. As such it is possible for math.random() result to be equal to same function: result + 1 but from a different call. Extremely unlikely for them to match? Absolutely... but not impossible. 

     

     

  3. Hi 00Ghz,

    I think you could speed-up your algorithm and therefore the release date by getting rid of 2 unused variables in your code: workHarder, releaseFaster.  ;)

     

    You are only partially correct. Removing those 2 variables will indeed speed up the execution but will not impact the release date since they do not contribute to the formula ;)

     

    However those 2 variables do have an importance in real life. They relate to the fact that neither working harder or releasing faster, will result in more productivity or a better product (after a certain point).

  4. The release date is the date of its release, of course! ^_^

    Wasn’t that some sort of fallacy?

     

    Ok, let me put it in a language that the devs will understand. :D

     

    #quickRelease.h

     

    release = false ;

    releaseFaster = 0 ;

    releaseDate_ETA = math.random() ;

    workHarder = 0 ;

     

    while ( release != true ) {

        workHarder += 1 ;

        releaseFaster += 1 ;

        releaseDate = math.random() + 1 ;

        if releaseDate == releaseDate_ETA

             release = true ;

             println (releaseDate) ;

    } ;

     

     

     

     

  5. scrollbars on layers are also so irritating..

     

     

    please watch following video i uploaded on youtube. 

    https://youtu.be/Nej6vH_zlWs 

     

    I added many layers, now when I scroll them up or down, a scrollbar appears on layers and that takes a second to hide. that also causes interruption what layer we needed to click. because one accident click on scrollbar will move/scroll layers upwards or downwards.  

     

    This has been reported looooong time ago. Still no fix :(

  6. What? You mean that in future I’ll be able to trash my Justinmind subscription, Quartz Composer or Origami?

     

    Matt are you working on a prototyping tool in AD? :)

     

     

    Thank you, Matt, for this explanation …   :)

     

    (Exactly, I was thinking that you could apply constraints to your objects within an [almost] arbitrarily sized artboard and have the app relayout your contents according to your directives on the device. Hmm, I am just thinking … what about a true Prototyping persona in the future? Wouldn’t that be a killer feature for UI and Web designers?)

    Was thinking the same thing. That’s how it should work ideally. Not just get some snapshot of the current artboard.

  7. Hi,

     

    I noticed that the symbols properties when dealing with text is not very smart about what changes I make and what to still keep in sync.

     

    For example made a text in a symbol. I changed the text content. Pressed sync again.

     

    However when I tried to change the color afterwards to another symbol duplicate, the desynced text layer , didn’t change the color as well.

     

    Since I only edited the text content itself and not any other properties, the color should still be in sync. 

     

    However the same thing works as expected on normal objects.

     

    Is it a bug?

     

    Thanks,

    Vlad

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.