Dyalog Forums

Here's a bit of additional information: The EV3 "brick" has Bluetooth as does the Mac Book Pro, so with the existing hardware and installed drivers I should easily be able to pair the devices. The question is: once they are paired, how can I send a payload of data from the Mac to the EV3 and then ...

Want to talk to a Lego Mindstorms EV3 brick using Bluetooth. My platform of choice is a Mac Book Pro. Can anyone here help me connect the two. I'd like to establish simple synchronous communication at first. Thanks for any help.

Morten, If you look at my Form class a simple read-only property is all that's required to query the subobjects of a form. I'm not sure why Maria feels this is an issue. Since you have to store them anyway (I just use a vector), this can't be much simpler. I suggest if you are interested in ...

Re Maria's last post. I must admit that I found the necessity of having to create a control within the context of the form it belonged to counter-intuitive. I'd first tried to create them independently (oddly enough the tab control and subform have a mechanism that allows this sort of thing). Also ...

I think you want to do this assignment in a constructor, otherwise each instance of CollectionProperty will share the same instance of Collection.

Hi JoHo, I understand that it's a screen design system that was written before Dyalog introduced classes and as such it is not truly OO. I think this will return Maria to the "bad old days" from which she wants to emerge. I'm sure it's a good system, but I hope Dyalog modernizes it to use real ...

Hi Maria, You ask a number of questions in your post and I'm not sure I understood all of them. I'm relatively new to the GUI stuff, but have opted to go with the "Good []NEW Days." For consistency's sake, I derive a class from every GUI "object" I use including items like Separator for which there ...

Thanks for posting this. Does it work for derived classes?

Not sure why they consider the thread as holding a separate reference to the object -- this might be a bug. I guess you can define a property to shut down the thread and sit in a wait loop till it terminates. Then you can do your )erase.

Jane, :class Foo {del}Foo :implements constructor :access public {comment} kick off the new thread here... {del {del}NoFoo :implements destructor :access private MyThread.Done<-1 {del} :endclass MyFoo<-[]NEW #.Foo You can kick off the thread in MyFoo's constructor. When you ")erase MyFoo" the ...