First, I think the New Promoted Event tool is very nicely done and it is so nice to be able to edit/compile promoted events directly from the IDE.

One of the features I like is the warning icon it gives you if you appear to be creating a promoted event that already exists:

OI10-PromotedEvent-Warning.png?rlkey=cfzen8asrq52ntxelxkvw9z8l&dl=1

However, I noticed that I can pick one of my existing forms:

OI10-PromotedEvent-NoWarning.png?rlkey=p84zvnnk2h2wsezkriqhuclsk&dl=1

Two questions:

1. Isn't this just creating a script event for my form?
2. If so, then why do I not get the warning icon? As you can see, I already have a script event.

Don Bakke

SRP Computer Solutions, Inc.

@DonBakke

How did you get those images to display so well?

@DonBakke

How did you get those images to display so well?

Hi Barry - I'm not certain what you consider "so well" about them, but I used the same technique I've always used for years. I use SnagIt (or Windows Snipping tool if on another machine) to make the screen capture. I then save this as a PNG to a specific folder I use for forum posts. This folder is managed by Dropbox. I then use the Copy Dropbox link feature to give me a link to the file which I then paste into the Picture feature on this site. Note, I change the ending of the Dropbox URL from dl=0 to dl=1 so the image renders within the message correctly.

Don Bakke

SRP Computer Solutions, Inc.

@DonBakke

How did you get those images to display so well?

Hi Barry - I'm not certain what you consider "so well" about them, but I used the same technique I've always used for years. I use SnagIt (or Windows Snipping tool if on another machine) to make the screen capture. I then save this as a PNG to a specific folder I use for forum posts. This folder is managed by Dropbox. I then use the Copy Dropbox link feature to give me a link to the file which I then paste into the Picture feature on this site. Note, I change the ending of the Dropbox URL from dl=0 to dl=1 so the image renders within the message correctly.

Don Bakke

SRP Computer Solutions, Inc.

Ah, ok, the old standard.

Thought I saw mine a while ago just being links.

I will update my KB just in case I have it wrong

Ah, ok, the old standard.

Thought I saw mine a while ago just being links.

I will update my KB just in case I have it wrong

There are different types of Dropbox links. File sharing links are sometimes used by mistake and this doesn't work as a way to display the image in the post. What I didn't mention in my previous post was that I use Windows Explorer to navigate to the folder where my images are and then I right-click on the image to pull up the Copy Dropbox link menu.

Don Bakke

SRP Computer Solutions, Inc.

Ah, ok, the old standard.

Thought I saw mine a while ago just being links.

I will update my KB just in case I have it wrong

There are different types of Dropbox links. File sharing links are sometimes used by mistake and this doesn't work as a way to display the image in the post. What I didn't mention in my previous post was that I use Windows Explorer to navigate to the folder where my images are and then I right-click on the image to pull up the Copy Dropbox link menu.

Don Bakke

SRP Computer Solutions, Inc.

Ah, ok, the old standard.

Thought I saw mine a while ago just being links.

I will update my KB just in case I have it wrong

There are different types of Dropbox links. File sharing links are sometimes used by mistake and this doesn't work as a way to display the image in the post. What I didn't mention in my previous post was that I use Windows Explorer to navigate to the folder where my images are and then I right-click on the image to pull up the Copy Dropbox link menu.

Don Bakke

SRP Computer Solutions, Inc.

Awesome, thanks!

Hi Don,

Some background: There are seven types of promoted events in the system split into two categories: the common "G" (Generic) ones, and "S" (Window Specific) ones. You can see how they map onto the repository keys now that promoted events are tracked there:

   // G1) SYSPROG*LOSTFOCUS.EDITFIELD.OIWIN*   -> SYSPROG*PROMOTEDEVENT*LOSTFOCUS*EDITFIELD.OIWIN

   // G2) SYSPROG*LOSTFOCUS..OIWIN*            -> SYSPROG*PROMOTEDEVENT*LOSTFOCUS*_.OIWIN

   // G3) SYSPROG*..OIWIN*                     -> SYSPROG*PROMOTEDEVENT*_*.OIWIN

   // G4) SYSPROG*LOSTFOCUS.EDITFIELD*         -> SYSPROG*PROMOTEDEVENT*LOSTFOCUS*EDITFIELD

   // G5) SYSPROG*LOSTFOCUS*                   -> SYSPROG*PROMOTEDEVENT*LOSTFOCUS*_

   //

   // Or one of the WINDOW-specific types

   //

   // S1) SYSPROG*LOSTFOCUS.EDITFIELD*<winID>  -> SYSPROG*PROMOTEDEVENT*LOSTFOCUS*EDITFIELD^<winID>

   // S2) SYSPROG*LOSTFOCUS*<winID>            -> SYSPROG*PROMOTEDEVENT*LOSTFOCUS*^<winID> 

The ones you refer to are the "Window-Specific" promoted events.

I.e. they apply to all events of that name, and/or that control type, for a specific form.

In the case you highlighted you'll see a subtle difference in the event key between the normal script event and the promoted one - the latter is missing a trailing ".".

So for a WINDOW type, for a WINDOW-only event (like READ), these would seem to be pointless - you might create one for something like a control-based event like CHANGED for a specific form, but you'd never create one for READ because it would offer no advantage over a normal READ event for the form - it's essentially a duplication, so to answer your question:

Isn't this just creating a script event for my form?

Effectively yes, it is.

Basically, as far as I can determine, they are something of a relic of days gone by - some of the very early OI tools, like the original report builder (ORVIEW?) used these types of events before the Form Designer was written (Gene built ORVIEW "by hand" IIRC), and you should see them in the SYSREPOSEVENTEXES table in your earlier OI systems.

If so, then why do I not get the warning icon? As you can see, I already have a script event.

Indeed, but as you can see they are actually two different things, and if building OI10 has taught me anything it its that as soon as I remove something, then someone, somewhere, will tell me that they need it :)

So they have been left in, they are what they are… of course what might be nice is a warning that there is a "normal" event of the same name, so that could be an enhancement post 10.2.1

Regards,

Carl Pates

In the case you highlighted you'll see a subtle difference in the event key between the normal script event and the promoted one - the latter is missing a trailing ".".

Actually, I had noticed that subtle difference, but just assumed it was an oversight in how the key was being represented. Now that you have explained things as you have, everything now falls into place.

Thank you for explaining this to me.

Don Bakke

SRP Computer Solutions, Inc.

View this thread on the Works forum...