https://linen.dev logo
Powered by
# haxe-ui
  • r
    On the 
    name
    field of my extern since it's a 
    ConstCharStar
  • b
    how does Star differ?
  • l
    Star is the newer type and is much easier to use if you want to interact with a pointer to a class or struct as you can use standard haxe field access and the generated cpp will automatically dereference the pointer
  • b
    interesting
  • l
    Copy code
    haxe
extern class MyExtern {
    var field : cpp.ConstCharStar;
}

function main() {
    final ptr : cpp.RawPointer<MyExtern> = foo();
    trace(ptr[0].field);

    final ptr : cpp.Star<MyExtern> = foo();
    trace(ptr.field);
}
    difference between using raw pointer and star
  • r
    Or more specifically: @User
    Copy code
    var dirPtr = DirEntFunctions.open(".");
var dirEntries = Pointer.fromRaw(DirEntFunctions.read(dirPtr));

Sys.println(dirEntries.at(0).name.toString());
  • l
    both represent a raw c pointer but the second example will dereference the pointer to access the field (generates something like 
    (*ptr).field
    )
  • b
    super interesting, so i had it backwards... its RawPointer that is limited (although the C array access is important / useful)
  • l
    yeah, you can't use array access on star and const star
  • l
    I think the intention is that you use star for most pointer extern stuff now since some a lot of the cpp.Lib and other stuff only returns Star instead of RawPointers
  • l
    but you can cast between the two no problem since they're both real c pointers
  • b
    good to know... thanks for the insight / enlightenment. I might have a play with changing raylib to use Star and see how it pans out - athough i defo need array access for some of them (but certainly not all)
  • b
    and then maybe... ... maybe... hxWidgets 😮
  • b
    (that wont be fun)
  • l
    I've been meaning to open a PR to the haxe manual or something to document the three different hxcpp pointer types (RawPointer, Star, Pointer) since I only learnt the difference through experimenting and looking at the output cpp
  • b
    yeah, i didnt really look deeply into Star, i just kinda went "meh, its an old version that probably isnt used"... ... little did i know that was arse about face 😄
  • b
    thanks again Aidan - thats really useful info 👍
  • r
    That would be really useful but I would have deprecated the old RawPointer and RawConstPointer and renamed the star ones to RawPointer It can be pretty confusing now, since the std doesn't document them Nonetheless thanks for the insight
  • r
    But by experimenting you can just convert a Star to a Pointer and then work on top of it
  • b
    well, rawpointer still has a purpose
  • b
    ... ... ... C array access
  • b
    i think ill mess around with the raylib-haxe generator to see if i can get it to use Star or RawPointer (depending on if its an array or not) and see if that a) works and b) breaks any of the haxe samples
  • r
    I should rework the hxRalyib bindings also, since they all use the wrapper class (I didn't know at the time the difference between the different types of pointers 😅 )
  • b
    oh, yeah, they use Pointer in the externs... thats probably a pain to work with
  • r
    I've made the PR (the bindings were incomplete and I've just went with Pointer, fortunately with the magic of regexp substitution it will be easy to fix)
  • b
    is there a small example of drag and drop? I want to have an absolute layout where I can place images that I can move around in this layout with the mouse.
  • b
    there is no built in d&d
  • b
    actually, hang on, there is now
  • b
    I mean I have seen something like that. But that was a little longer ago.
  • b
    i think you can just do "myComponent.draggable = true"
1...829830831...1687Latest