OEM Codes...

[Arbo]

If I make a button and use say, OEM Zero X, then go back and look at the button,  it shows up as user defined, though the code # is correct.  But the button doesn't work.  But if I use the STD zero X, with the depreciated code, it works fine.

Is this a known problem?

[Klaus1311]

Hey,

if I understood the wiki right, the codes you are talking about, are for programming purpose. For designing the standard codes are for the predefined actions



Klaus

[Arbo]

Perhaps I am confused then...  why are the OEM codes available to pick for a button if only the STD ones are 'correct' ones to use?

Other than that, great program, it's the only screen designer that even runs for me.  Loving it so far.

[Arbo]

Klaus,

Perhaps I can explain a bit better.   Say you are working on a 100% new screen.   Create a background, create a page 0 screen with a global reset button.   Set the button to 'OEM Reset' and it changes in the data field to 'user defined: *********x' (don't remember the number).  Save it, the reset does not work.  Go back and change it to 'STD Reset'  and save it, the reset button works.

Same thing with OEM Load vs. STD Load.    It's all good I guess as long as there is a STD function that is the same as the OEM function, but if not.....

Odd thing is if you load the default 1024.set, the load file, edit file and other things are set up as using the OEM codes, and show up correct in the details window rather than user defined: *********x....

I have attached pictures that show this behavior....  first one is setting the reset button to OEM Reset, which changes to "user defined"...  next is using STD Reset...    last shows how default screens come up with proper OEM codes.

[Arbo]

I think I figured out what must be going on.   If you create a button from scratch it will assign properly.   If you create an image-button from scratch, when it saves to the SET file, it saves the OEM code (ie, 216 for load file) but it doesn't set a bit saying it's an OEM code.

Figured this out by running screen3 on the screen and clicking on the buttons that do not seem to work right, and it brought it up with the right # code, but no option (ie, OEM) bit set.

Hope that clarifies.

[ger21]

Hey, you stole my reset!!

[Arbo]

Yeah, that is it.  I might even steal your cool aqua buttons.       Your screen is awesome.

[Arbo]

Klaus?  Have you read any of this?

[Klaus1311]

Hey Arbo,

sorry I didn't answer earlier. There is no bit specifying a OEM-code. When you "add" a control you have to assign a function. Depending want function you want, you select either OEM or standard code. When you are using an OEM code, the decimal code is shown in the OEM_code line. The naming is taken from the wiki. The OEM-codes are for programming purposes e.g. SetOEMLed. As I wrote earlier, to assign a function to a control, use the Std calls.



Klaus

[Arbo]

Ok, I guess I'm not being clear, and will have to give up modifying my screens as now none of the screen programs work.

Do this, open the default 1024 set, click on some of the controls, you will see they are OEM controls, in fact, there are not STD
controls for some functions (I believe edit gcode is one of them).     Now that you see that,  create a brand new screen  you don't
need a background, on that screen, add an image button and set it to an oem function like load gcode.  Watch what it does.

Now create a normal button and assign it the same function, and watch what it does.

You will see the button works, but the image button does not.

As a former programmer, I'm just trying to let you know on the image button save, something is missing, a bit is not being
set if it's an OEM code.

I hope I am being clear as I'd like to continue to use your program, but can not until this feature works correctly.