Hi Tom, can I summarise by saying,The use of macros is less CPU intensive. The more code you can put into a macro, the better.Also, using Select/ Case is not very CPU intensive. This presumably is less intensive than a load of Visible statements.Ref an example above, I can't think at this time of the morning where you would use if/els for displaying multiple bitmaps. Obviously this can be used in Select/ Case, but I'm thinking the way the question was put, it was being used another way.cheers,nick

>The use of macros is less CPU intensive. No way. There is no advantage in terms of assembled code efficiency with the use of macros. The only benefited is the programmer that has to write less lines (and an improvement of readability too IMO), but that's all.>The more code you can put into a macro, the better.Most of times this is true. But because of the reasons stated above.>Also, using Select/ Case is not very CPU intensive. This>presumably is less intensive than a load of Visible>statements.We'd have to separate this in two parts:Code is what we know the most common way of managing pure code within a stack's area. When used to support logic only, is not needed because there is no bitmap to show.Typical example would beMake the hydraulics workI would assume like you that there is not much CPU cost here.Now, when there is a need to show bitmap(s), enters in action.And for sure in this case there will be a hit in performance, because bitmaps' display consumes a lot of CPU (and FPS) power.>Ref an example above, I can't think at this time of the>morning where you would use if/els for displaying multiple>bitmaps. Obviously this can be used in Select/ Case, but I'm>thinking the way the question was put, it was being used>another way.As I posted on this same thread earlier, if/els are components of the stack, and they only "push" values that can be tested by statements.Tom

Tom,fps, bitmaps, value, visible etc...How do you program knobs with backlighting (like the in the 757)?I still need 2 elements.One for the knob and one for the overprojected backlighting when on.Jan"Beatus ille qui procul negotiis..."

>Obviously this can be used in Select/ Case, but I'm>thinking the way the question was put, it was being used>another way.I was hoping to use Case structures to decide what code to use after the Case structure determined the situation... but if it can only apply to bitmaps, that appears to be a serious limitiation. It's a shame that we can't put logic there or, apparently, even a nested Element within the Case that would handle the logic within the nested Element.IE:0 (>L:OnGround,bool)OR (stack) 'Down' sp30 It would be nice... maybe someday.Scott / Vorlin

Do you mean something like this?http://forums.avsim.net/user_files/145769.jpgI guess I can't reinvent the wheel here...Same as you, two bitmaps for the switch.Now, if only Transparency tag would work for Circle command....Tom

>I was hoping to use Case structures to decide what code to use>after the Case structure determined the situation... but if it>can only apply to bitmaps, that appears to be a serious>limitiation. It's a shame that we can't put logic there or,>apparently, even a nested Element within the Case that would>handle the logic within the nested Element.>In fact what IS logic it that we can't put extra (stack) code inside a .AFAIK, those structures surrounded by "<>" (like ) are nothing but pointers to certain areas of memory in the assembled codeStrictly speaking of , when the code is compiled, each Case value is associated with a memory location where its corresponding bitmap resides. So, when a stack value is extracted with a command, it is compared against the array of defined pointers (Case's) and the matched pointer will redirect the code to the memory area that contains the bitmap to be displayed.Within this logic, I guess there is no room for other type of code.Tom

Hi Tom, thanks for being your usual very helpul self.>Now, if only Transparency tag would work for Circle command....I had cause to use a transparent circular element recently, so used a bitmap with alpha (originally intended for shadowing). I presume you know this technique?cheers,nick

>>I was hoping to use Case structures to decide what code to>use>>after the Case structure determined the situation... (snip) It's a shame that we can't put logic there or,>>apparently, even a nested Element within the Case that would>>handle the logic within the nested Element.>>>>In fact what IS logic it that we can't put extra (stack) code>inside a .(snip)>...when a stack value is extracted with a command,>it is compared against the array of defined pointers (Case's)>and the matched pointer will redirect the code to the memory>area that contains the bitmap to be displayed.>>Within this logic, I guess there is no room for other type of>code.I got the idea in general, but I'm getting the impression (and it could be a wrong impression!!!) that you seem to think this is very simple to understand... and with your background and experience, I imagine it is! (smile)Unfortunatly, I come from a background where it's very common to write a Select / Case in the way below and I was wondering if it could be emulated in MSXML for FS9: Food @PizzaMacro @EnchaladaMacro @ChineseMenuMacro In my background, selecting what function or macro to do next depending on the results of a Select (Switch) argument is considered to be a great way to write your script.But, if I understand you correctly, MS designed the CASE tag so that it's code is assembled to include the functions of an IMAGE tag and we can't get rid of that so that we can use the CASE for something other than displaying a bitmap because the CASE tag itself is going to be assembled into code that tells FS9 to display the image contained within the CASE tags no matter what.So to write: @PizzaMacro Would be assembled into final code that tells FS9 "if the value is equal to zero" then:"@PizzaMacro"Which would, of course, fail miserably.Wow... after all that time learning to use Case to branch from function to function for my other projects outside of FS9, this leaves me a little stunned. Oh well, nested if's haven't been taken away so there's always a way to do what we need to do.Thanks,Scott / Vorlin

Yes, indeed I use alpha masks in some of my gauge (ie Stdby Attitude), however I couldn'd get fair results with small bitmaps (switches).I'm gettin axious waiting for FSX arrival.. :-(Tom