Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Toomas Vooglaid
    @toomasv
    No. But will try this too. Thanks for reminding!
    hiiamboris
    @hiiamboris
    :+1:
    at some point after setting "enable live log", clicking on the status bar stopped to bring up the log window, but I can't repeat it anymore
    Toomas Vooglaid
    @toomasv
    Ok, will look at this too.
    hiiamboris
    @hiiamboris
    and it crashes on export when I make the canvas a bit bigger:
    Toomas Vooglaid
    @toomasv
    It is no worth to torture style in current release. As said, there is a bug that makes it unusable..
    hiiamboris
    @hiiamboris
    but this is probably image! limitation or smth
    or to-image
    Toomas Vooglaid
    @toomasv
    -e did not help :(
    hiiamboris
    @hiiamboris
    ):
    Toomas Vooglaid
    @toomasv
    min-size 300x50 produced 13724 x 25487 png of red-lexer
    hiiamboris
    @hiiamboris
    should be just 1.4GB (in RAM)
    oh
    Toomas Vooglaid
    @toomasv
    3,39 MB
    hiiamboris
    @hiiamboris
    compressed
    I know where the crash is, will report
    hiiamboris
    @hiiamboris
    red/red#4853
    meanwhile I suggest DG reports that it cannot save an image bigger than 500 megapixels, instead of crashing
    GiuseppeChillemi
    @GiuseppeChillemi
    Is any command line viewer for rules planned?
    Toomas Vooglaid
    @toomasv
    Please explain in more detail what do you expect it to do.
    GiuseppeChillemi
    @GiuseppeChillemi
    Take a rule set and display the canvas on a stand alone, scrollable window with no other features; otherwise, using a command switch, save it to a file
    Gregg Irwin
    @greggirwin
    There is no "diagram viewer" mode. We talked about it, but since the app is free to use (just with a watermark), we suggest people use the real thing.
    Toomas Vooglaid
    @toomasv
    There actually is an experimental viewer from the time I experimented with the idea. It has many functions hidden and only shows the canvas.
    GiuseppeChillemi
    @GiuseppeChillemi
    I would like just to show and eventually generate and save the canvas.
    hiiamboris
    @hiiamboris
    You can generate it from command line then show it using your favorite image viewer
    Gregg Irwin
    @greggirwin

    @hiiamboris you can, but that's so clunky compared to hover popups, ctrl+wheel to scroll by rule, etc.

    If you can't edit, though, why would you be able to save @GiuseppeChillemi? Or is it so you can use an external editor, not for giving users a viewer?

    GiuseppeChillemi
    @GiuseppeChillemi
    If you can already generate and save it from command line, without opening any window, there is no need for a viewer.
    Gregg Irwin
    @greggirwin
    You can, read the CLI section in Help.
    luce80
    @luce80
    I have updated Win 7 with link @greggirwin provided and now it starts. There are still some gui "glitches" and when I type the second quote the program disappears.
    ice-video-20210322-082722.gif
    Gregg Irwin
    @greggirwin
    Great! That's a bug we can try to reproduce. Can you post your rule and input files for testing @luce80 ? Also, try turning off Live rendering to see if the crash still occurs.
    hiiamboris
    @hiiamboris
    @toomasv I've updated my console-on-demand script some, and usage instructions. Maybe it'll work for you now;)
    luce80
    @luce80
    @greggirwin If I turn off Live rendering crash happens earlier ! As soon as I type the first quote.
    stl: [
            solid pos: ['facet :pos | word!]
                some facet
            'endsolid to end
        ]
        facet: [
            'facet 'normal triple
                'outer 'loop
                    'vertex triple
                    'vertex triple
                    'vertex triple
                'endloop
            'endfacet (
                ;if (tri-count // 1000) = 0 
                [
                    if verbose [prin "."]
                    ;set-face info-text append get-face info-text "#" 
                    ;set-face info-text rejoin ["" to-integer tri-count / poly_count * 33 "%"]
                ]
                tri-count: tri-count + 1
    
            )
        ]
        triple: [copy point 3 number!]
    solid
     facet normal 1 0 0
       outer loop
         vertex 10 0 0
         vertex 10 10 0
         vertex 10 10 8
       endloop
     endfacet
     facet normal 1 -0 0
       outer loop
         vertex 10 0 8
         vertex 10 0 0
         vertex 10 10 8
       endloop
     endfacet
    endsolid
    Toomas Vooglaid
    @toomasv
    @luce80 Shouldn't solid be lit-word?
    Gregg Irwin
    @greggirwin
    If the input is a string, I think @luce80 means he's trying to make solid into "solid" when the crash happens, based on the GIF above.
    But I agree that doesn't match how 'facet is used.
    Gregg Irwin
    @greggirwin
    I can dupe the crash, but not with 100% consistency. It only happens if I have Live Input Parsing on. Then, by adding and deleting quotes, around solid it will crash after a few edits.
    luce80
    @luce80
    @toomasv Yes the main rule is wrong because I was in the middle of "converting" it. I wanted to tweak my rule with DiaGrammar and soon discovered that it cannot parse "loaded" rules and input (or I have not understood how to do it)) so I started the boring job of converting lit-word!s to string!s and ...crash
    Toomas Vooglaid
    @toomasv
    @luce80 Sorry for delay in answering!
    DG can parse loaded rules. Just uncheck "String" checkbox on Input area's toolbar. I'll include a gif showing debugging your rule (click to see bigger):
    debugging
    Toomas Vooglaid
    @toomasv
    Explained:
    1) Uncheck "String".
    2) Try, if parsing some simpler rules or part of rules works.
    Easiest way is to select a rule or part of it in grammar and corresponding fragment in input against which the grammar-selection should be tried.
    Green check or red cross should appear to show success or failure.
    3) If neither green nor red mark appears, internal error must have occurred when selected part of grammar was loaded, so that it hanged.
    But it was not syntax error - this would have turned "GRAMMAR" label red.
    (In your case this must have happend inside parens, as before parens were selected, grammar worked)
    To enable it again, make some little edit in grammar to force loading it again (provided "Live" on canvas toolbar is checked; alternatively use F5 to refresh).
    4) Checking parens notice that there are words without value: tri-count and verbose. Add these words to grammar.
    (none and logic! values, and also functions and objects you add to grammar are not shown on canvas to not clutter the picture, because these are helpers)
    5) Check selections again. If they work, unselect everything both in grammar and input. This guarantees that input will be parsed with the rule in "Rule" dropdown (preferably rule that should match whole input).
    6) Parsing with rule in dropdown shows failure - according to your stl rule input needs to include endsolid but it does not. Add this.
    7) Parse. Todo bien.
    luce80
    @luce80
    @toomasv Thanks for the visual help!. I like the "selected" to "selected" check quite a lot, albeit it requires a bit too mach manual dexterity ;) . Perhaps add some kind of "markers" ? Just a suggestion.
    luce80
    @luce80
    On Win 7 in v.1.2.2 the "aesthetic glitch" of edge and divisor lines not moving and not resizing when moving the gui splitters is still present.
    luce80
    @luce80
    On Win 7 in v.1.2.2 immediately after resizing the window you cannot drag the GRAMMAR scroller knob, you can move it only after clicking somewhere else .
    luce80
    @luce80

    On Win 7 in v.1.2.2 same sudden crash as before but now with a bit different process. Do what @toomasv did to make things work except simply comment this line:

    tri-count: tri-count + 1

    then go to this line

            'solid pos: ['facet :pos | word!]

    and starting from the end of the line erase with backspace:pos | word!], then starting from just after the [ erase with backspace until...crash.

    hiiamboris
    @hiiamboris
    I've found out today that Microsofties are using this diagramming tool
    Having interactive HTML output seems great.
    Toomas Vooglaid
    @toomasv
    Yes, this was one of our initial comparisons.
    hiiamboris
    @hiiamboris
    ok so HTML output is on the roadmap I presume
    Toomas Vooglaid
    @toomasv
    On wish-list, yes.
    Gregg Irwin
    @greggirwin
    SVG is the first step in that direction, for the diagrams themselves. I don't know that we'll do HTML directly, but could have a plugin or specific tool for diagram pages. This also aligns with RAPIDE, and how APIs are documented and presented. From a business standpoint, I think we'll be forced to offer a browser-based alternative there.