Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 17:42

    dockimbel on master

    FEAT: minor comment addition. (compare)

  • 17:29

    dockimbel on master

    FIX: makes do/trace re-entrant.… (compare)

  • 10:04
    hiiamboris commented #5004
  • 00:07

    dockimbel on master

    FIX: interpreter events CALL an… (compare)

  • Dec 06 22:33
    gregit opened #5004
  • Dec 06 22:12

    dockimbel on master

    FIX: error in debugging tools w… (compare)

  • Dec 06 17:09
    hiiamboris opened #5003
  • Dec 06 17:09
    hiiamboris labeled #5003
  • Dec 06 16:27

    dockimbel on master

    FIX: minor code improvement. (compare)

  • Dec 06 14:16

    dockimbel on master

    FEAT: minor code improvements. … (compare)

  • Dec 05 23:30

    dockimbel on master

    FEAT: filter out properly by de… (compare)

  • Dec 05 18:36

    dockimbel on master

    FIX: a compiler internal data s… (compare)

  • Dec 05 11:48

    dockimbel on master

    FIX: missing variable in interp… (compare)

  • Dec 04 02:05

    dockimbel on master

    FIX: avoids compiler crashing i… FEAT: adds `set-trace` routine … (compare)

  • Dec 01 19:49

    dockimbel on master

    FIX: several fixes to profiler.… (compare)

  • Dec 01 16:30

    dockimbel on master

    FIX: profiler erroring on anony… (compare)

  • Dec 01 13:31

    qtxie on master

    FEAT: adds support for custom h… (compare)

  • Dec 01 12:41

    dockimbel on master

    FEAT: a few minor improvements … (compare)

  • Dec 01 01:14

    dockimbel on master

    FIX: missing entry for %tools.r… (compare)

  • Dec 01 00:51

    dockimbel on interp-events

    (compare)

packetrhino
@packetrhino
@greggirwin yes please do keep me in the loop
JacobGood1
@JacobGood1
@9214 and an easily extensible ide for those dialects
Rudolf Meijer
@meijeru
I have downloaded the latest red.exe for Windows (22-Sep-2019, sha: 7daa2dd5) and compiled the console (yielding gui-console-2019-9-22-34786.exe) but, strangely, when I ask for about, it gives me Red 0.6.4 for Windows built 20-Sep-2019/18:03:51+02:00 commit #04daa5e, which is a much older version. What am I doing wrong? Also, I can't see a commit with sha: 7daa2dd5 anywhere.
So far, one explanation seems to be that red-latest-exe has not been updated.
Gregg Irwin
@greggirwin
What OS? I don't see a 7daa2dd5 for any of the SHAs on the download page.
04daa5e is from 20-sep.
Nenad Rakocevic
@dockimbel
@x8x ^---
Rudolf Meijer
@meijeru
@greggirwin I am on W10. 7daa2dd5 is part of the filename. Is that not the sha of the latest commit going into the latest .exe?
Rudolf Meijer
@meijeru
@x8x Progress site is again not up to date: latest commit on red/red/master (23 hours ago) does not show up.
Rudolf Meijer
@meijeru
Also, date of start of week is not shifted to 23 sept
FLuX LoOP
@x8x
Checking..
FLuX LoOP
@x8x
progress is fine, will have to investigate some JS timeout issues, JS is a mess..
Rudolf Meijer
@meijeru
:+1:
Rudolf Meijer
@meijeru
I am looking for the Wiki entry that lists the functions that still have TBD in their specs. It was recently made but not findable from the Wiki main page. Help!
Vladimir Vasilyev
@9214
@meijeru here.
Rudolf Meijer
@meijeru
Thanks to Ian Nomar for making this. I did an exhaustive scan of the pre-defined functions, and the only one he missed is request-dir which has a /multi refinement to be defined.
Gregg Irwin
@greggirwin
@meijeru I thought that signature part came from the build webhook, but can't find the details right now to verify. @x8x? :point_up: September 23, 2019 12:29 AM
FLuX LoOP
@x8x
All is good now, small issue related to the git submodule experiment.
Gregg Irwin
@greggirwin
Thanks for jumping on that @x8x!
Rudolf Meijer
@meijeru
I confirm. Thanks!
FLuX LoOP
@x8x
@meijeru Thanks for watching our back and reporting! Much appreciated :smile:
Gregg Irwin
@greggirwin
@meijeru on red/red#4047 the behavior is easy to reason about, but you're correct that it's not documented. It is by design however, as there is explicit integer handling logic. @gltewalt, would you please add an example to the image! docs?
Oldes Huhuman
@Oldes
@greggirwin I must disagree again with you. I consider @meijeru issue to be a bug. Sorry.
@greggirwin regarding your ask on chat comment... I don't like it either.. it is easy to lost info in these chats and quite often there is no response, like in this another buggy case
Gregg Irwin
@greggirwin
If someone says "Is this intended?", it's a questionable ticket. If we chat, and agree it's ticket-worthy, then we put it in a ticket. That simple.
If it's a bug, then it's either a design bug, and should be addressed as such, or a genuine bug, in which case we need to determine the correct/expected behavior.
Rudolf Meijer
@meijeru
I can reformulate it as a genuine bug by saying: since it has not been documented anywhere and is not obviously by design (at least not to me), I say there should be an error message that it is forbidden. That may then be dismissed by the Red team with proper justification and motivated interpretation of what it does.
I don't buy the argument of explicit integer handling, because one integer could also be interpreted as four bytes (RGBA).
Nenad Rakocevic
@dockimbel
FYI, we have a WIP red/red#4049 on changing the underlying pair! type to use float32! components instead of integer!. As using floats for pairs is not always desirable (because of side-effects in float handlings), we are considering keeping the pair! as is, and introducing a new similar 2D type, but relying on floats. The hard part, as usual, is coming up with a proper syntax for such type (in addition to a proper name). So we are proposing coordinate! for such new type name and using the same syntax as pairs, but with mandatory decimal markers, e.g. 1.0x2.0. Such type would allow also an optional third coordinate. Would such syntax be acceptable?
Respectech
@Respectech
Would it be possible to also allow 1.x2. as
... a shortcut like it was possible in Rebol?
Petr Krenzelok
@pekr
shorter name could be coord!, but not sure Redbol land likes such abbreviations :-) OTOH, isn't float and abbreviation too?
As for the syntax, I have no idea what other syntax proposals could look like? So as for me - yes, the proposed syntax looks ok to me.
Toomas Vooglaid
@toomasv
Very welcome extension!
R cqls
@rcqls
Excellent!
Petr Krenzelok
@pekr
btw - how could GUI benefit from a subpixel accuracy?
Boleslav Březovský
@rebolek
@pekr AGG-based Draw allowed for subpixel accuracy and it certainly helped a lot.
Nenad Rakocevic
@dockimbel
An alternative name for such type is point!.
hiiamboris
@hiiamboris
@dockimbel I just wanted to say: Consider point! or point2d!. With a plan to have a point3d! in the future (surely this one will come handy). But you were faster :)
P.S. or point! can have a varying length, like tuple - 2 or 3 numbers
Boleslav Březovský
@rebolek

(...) but not sure Redbol land likes such abbreviations

coord(inate)! is based on float32! which is an abbreviation itself. :smile: Anyway, point! is a better name I guess.

R cqls
@rcqls
Good point for point!!
hiiamboris
@hiiamboris
Also. Can we not use the comma , instead of x for this new type? I always wondered why comma is never used for anything in Redbol. 1.0,2.0,3.0 or 1.0x2.0x3.0. Without syntax highlighting the first one reads a bit easier to my eye.
Qingtian
@qtxie
@hiiamboris We use comma , already.
>> 1,0
== 1.0
hiiamboris
@hiiamboris
I see. Pity :)
Qingtian
@qtxie

btw - how could GUI benefit from a subpixel accuracy?

One example is the caret in the gui-console. The position is not accurate for now. When you press Enter key many times in the gui-console, you'll notice it.

hiiamboris
@hiiamboris
Yes, think also of draw used with scale. Think of the points expressed in red/REP#34. Think of the red/red#3336 problem (computing the text size).
Boleslav Březovský
@rebolek
Custom GUI styles would benefit from it. I've got code in Rebol that is point!less (haha) to port to Red without floating pair!.
Petr Krenzelok
@pekr
Thanks for the answers re the subpixel accuracy usefulness. As for the name point!all the way ....
Toomas Vooglaid
@toomasv

@pekr Here is an example of subpixel accuracy importance. (You'll need also dftc.red and coffee).

If you run the file and stop the animation (by clicking on it) and then zoom into (wheel) then you might find the end-point of all the blue lines and see that orange line is drawn actually in a bit different place than the end-point of blue vectors. Blue ones are placed with sub-pixel accuracy, but orange line with pair!, i.e. pixel accuracy. (You can move the pic with mid-down dragging, ctrl-wheel to change rate).

Also, smallest circles are mis-sized and misplaced because there seems to be a lower limit on circle radius :)

Nenad Rakocevic
@dockimbel
@hiiamboris The comma syntactic treatment is a decade-long discussion about keeping or dropping comma as decimal separator. Maybe it's time to revisit it. Though it's a pandora box, the resulting discussions usually have low signal/noise ratio, as many people tend to express their personal opinions instead of giving factual arguments.