Jump to content

trevor

Mitglieder
  • Gesamte Inhalte

    264
  • Benutzer seit

  • Letzter Besuch

Alle erstellten Inhalte von trevor

  1. Anyone else having hard time knowing when to use a $ in front of a name in the event handler and when not to.... It seems a little arbitrary... Does anyone have a good explanation of how it works and when u need it.
  2. You can but maybe not in one step If u simply want to multiple variable 1 by variable 2 use the Set Variable function with *$Variable2 value. If u want to leave variable 1 unmolested you need to perform several steps. See test example below.
  3. Not really what I am looking for though Curt, I want to create a single variable name from a fixed set of conditions to reference some other variable or object. e.g. On a track section I know the Train_Name (Say "Coal_Train") , I can lookup the train speed so I know if it is going forwards or backwards, and I can tell by the track events if it is moving say East or West, So I want to lookup a variable list with the name "Coal_Train_Forwards_East", "Coal_Train_Forwards_West" etc. Ability to create simple FUNCTIONS would be great too... something like this.
  4. Specifically at the moment.. I want to lookup a NEXT action for a train when it enters a track section. Obviously I need to use the track section ID but I would also need to combine the entry direction into the track AND the direction of the locomotive itself (i.e is it reversing)
  5. I hope you are going to add this feature, the OTHER reason I'd like to do this is to combine variables to POINT at an object. e.g. "Track_" & Variable
  6. I'm trying to show some information in a label that combines several variables...How do I combine text values?
  7. I guess I just have not come across it yet..
  8. Hi yes I do understand the specific value methodology of the function. However I am trying to code a more generic system so that I can reuse as much of it as possible. In my example, the calling event passes a track section name to a common handler function. I did create a work around that uses two variables instead. The variable changed handler then looks up the value from the original variable. It works fine, but seems overly complicated. For numeric values you can do this by setting the lookup value to <9999999 or some such, but there is no such trick with text values.
  9. The event "Variable Is Changed" looks for a value. How do I make it trip for ANY value. Or more specifically, if it is a text variable how do I make it trip if I don't care about the actual content of the variable at that point?
  10. OOPS. Thanks for pointing out my error Yes I agree, perhaps the initial suggestion could be problematic. However, I still think the latter one might be considered. That is, select a group of tracks and click raise embankment or something.
  11. OK first I have to say thank you to the developer(s) for this application. I have been looking for something like this forever and am quite excited about the possibilities. I have been playing with it for a few days now and already have a list of suggestions. 1. Grouping and track sections. So you allow us to select multiple items and make them a group to manipulate and that is great. However, it would be wonderful if you could also make these groups act as a single entity, a track section, in the event handler. Case in point, while laying out track, virtual or otherwise, track segments are always combined into track sections with the intent that only one vehicle may normally enter said section at one time. This would make events like "vehicle on section" a lot easier to handle rather than having to enter a huge AND or OR statement. Said sections would also need to have the ability to attach variables to them. It would also be handy to combine multiple sections into another group "LINE" for those long single track systems so you can easily tell if something is coming the other way 10 sections away. This also leads me into #2 2. SIGNALS.. It would be nice if signals were somehow LINKED to track sections. In a simple world, when linked, entry signals into a section should be RED if a vehicle is on the section somewhere without the need to code all that. Perhaps with the augmentation of a Entry_Requested token state to also move things along. 3. Events 1. The event handler is ok as far as it goes, however, it is cumbersome to use in a large scale project and requires a LOT of duplication. The duplicate function helps with the latter, but it is prone to errors as you have to search for and change all the variables that are applicable to the new version. An added text based editor or export/import XML function would be fantastic. 4. Events 2. It would REALLY be great if you could tie handlers directly to objects. Currently you have the ability to create and set variables at the object level which is great, but it would also be nice to program specific functionality at that level too so that the event is automatically associated with the particular object. Once I have all the code written for my first engine, it would be nice to copy it directly to the second engine without having to change anything in the code. 5. Events 3. Arrays. It would be great if you could define some variables as an array to facilitate easier state-machine programming. 6. Events 4. Looping. Creating code such as "For each Locomotive", "For each variable in array", "For each Section" etc would significantly cut down on event definitions since you would not have to create duplicates for each object with the appropriate conditions or object selected. 7. Events 5. General Timers. I couldn't find a way to have a general timer start on project load or simulation start. I ended up using some other event to start one, but there has to be a better way. 8. Tracks 1. Ok so I get that you built a catalog based on real world model rail tracks and that is great work. However for those of us that have no intent to ever building the model in real life it would be fantastic if the FIRST track section was GENERIC. Then populate it with the most often used section types with the appropriate dimensional names . I find myself spending an inordinate amount of time searching for the right bit of track that I need and getting frustrated on not finding it. It would also be nice if it could automatically filter out tracks of the wrong gage for the current project.. 9 Tracks 2. Last section... I am sure we all do it, lay out a whole bunch of track then have space for one piece, but guess what, its a weird length. It would be nice if you could :STRETCH the last piece and have it snap to the next join. 10. Tracks 3. I get irritated trying to manipulate track pieces. I try to drag one and find it sloping or twisting or doing some other thing I did not want it to do. Perhaps have the mouse icon indicate which function you are currently hovering over, or perhaps better, a tool pallet that lets you select the particular function you want the mouse to perform. 9: Tracks 4: Elevation and slopes. OK I figured out how to use the editor to slope my track up a gradient but was hugely disappointed to find it floating in mid air. It would be nice if this was somehow attached to the contour pulling thing in the landscape so that an embankment was automatically drawn up with the track. Doing the latter manually is a REAL CHORE, especially on the sloping sections. That might be asking too much, but maybe a different tool that lets you select a track section and draw up the landscape to it... an auto-embankment as it were. 10. Middle mouse button rotation. What middle mouse button? Can I suggest SHIFT or CTRL right button as an alternative method. OK so all that sounds like I am complaining... really I am not. I just want to provide you with some developmental feedback and suggestions. I do realise I should not be holding my breath for any of them Best regards, Trevor
×
×
  • Neu erstellen...