I'm on the same browser, Win10, and the keyboard shortcuts are all working fine for me. :confused: cheers Chris Maunder

Hi Lukeer ! Returning a struct is indeed valid C. It's even given as example in section 6.8.6.4 of the C11 standard, which deals with the return statement. The return is done with a dumb bit by bit copy. This works very well for struct composed of fundamental types. But as soon as you have pointers in the struct, you need to be extremely careful about who owns an object and shall invoke (manually) the destructor: there is a high risk of nasty memory deallocation errors here ! The more efficient approach would be to return pointers as you suggested. But then, you'll have a high risk of memory leakage, in case the caller is not interested in the returned value (in other functions than the constructor). The safer way would be to design the API to encourage the caller to provide a pointer to the struture to be used, that he is responsible of (whether it's mallocated or local): class_animal a,*pa; newClassAnimal(&a); // reuse the existing structure pa = newClassAnimal (NULL); // or allocate a new one. // here the caller is aware that he has to manage the object I used very long time ago these kind of structures. The function pointers prove to be very efficient way to implement polymorphism in a non object language like C. However the management of the object has its drawback: no automatic destruction, and hence high risk of leakage for more complex execution flows, and especially if you use setjmp/longjmp.

congrats on the addition to the family, is it the usual yellow chick? You cant outrun the world, but there is no harm in getting a head start Real stupidity beats artificial intelligence every time.

He is gone now. Clean-up crew needed, grammar spill... - Nagy Vilmos

lukeer wrote: But it still shows a value as one line. That's what the PropertyEditor dictates; one property per line. You can "unfold" some of the properties (try the Font property in a WinForm as example), but that's as close as it gets. Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

lukeer wrote: Is there a bash way to achieve this? echo foobar > /dev/ttyS0 Use the best guess

Yeah, we have no idea what else he's got to control, nor how he has to refer to them. The LED=n might work for him but it really depends on the complete list of items he needs to control and the verb and value options available for each of those. When he knows that, then he might be able structure a standard format command line if there are a lot of possibilities or, if not, simplify it to what you've said. A guide to posting questions on CodeProject[^] Dave Kreskowiak

At my age, everything earlier than yesterday is "in the past". :sigh:

Try Fenster something. But really it should not be that difficult to find a German speaker in Germany who can help you. Apart from a couple of interludes last century I always found my German colleagues the most amenable and helpful people. speaking as ...

I ignore it. There are way more important things to care about. Probably because my score is so low, or maybe my score is low because I ignore it? I don't even know how all you folk track your downvotes or see where it is happening. I look for the links to find out every now and then, but never find it.

You can use a "post build event" to copy the file, the build event options are in your project properties. The build events are just typed in as if they were being executed from the cmd prompt (you can have more than one). Alternatively, you can make a simple script that'll set up the cd for you and even do the cd burning outside of your dev environment.

My fault. I'm used to code in C# but in this case the Visual Studio forum seems more appropriate. Let's continue there[^]. Ciao, luker

You may need to load the assembly into a separate AppDomain – but that then makes it impossible to copy the object across once it's loaded in the other domain, so it doesn't really help. With my lobby client (which loads its game type modules at runtime and does some version control on them) I had big problems trying to get two version of the same class to operate within one AppDomain. If the changes are more than just adding new fields, you might want to think about having the class unchanged and creating a new class which inherits from or wraps it. You might also want to look at the design: typically you should be serialising data, i.e. very simple data-containing objects, and I wouldn't expect them to change so much as to make the version tolerance in the framework insufficient. (The kind of thing you're experiencing here is one reason why I don't like to use [Serializable] for long term persistence, i.e. saving to file or other permanent storage. I typically have read/write methods on the persistent classes which convert them to the string or bytes that are needed to recreate each object – often not the same thing as its complete internal state, which is what serialisation saves – and those methods can handle the reading of prior versions, particularly if you pass as a parameter the version which the file claims to be.)

Goal: Have the WaitCursor over a disbled control I experimented a little bit on a small C# form app. Add a Panel to the form and make it the size of the Button you want to add. Add the Button to the Panel and set Dock = Fill (Panel obviously becomes the parent of the Button) Disable the Button (Enabled = false) Set Panel's UseWaitCursor = true When the the app runs, the button will be disabled and the WaitCursor will be visible over it. Conclusion: Use a parent panel to control WaitCursor visibility over a disabled control. It's extra work but you can have what your customer wanted. Cheers, Mike Fidler

I think you've run into a Windows quirk here. I've had this behaviour with other applications, and most of them weren't .NET. If the user is waiting for a while for the program to load/complete work, then it might be more elegant an idea to give more interface cues than just the wait cursor changing, such as a status text, or progress bar, etc.

My apologies for any redundancies or oversights for the previous posts on my part.... Bill