I just read other developer‘s complains about R6 Designer, and am willing to post my notices of weird behavior.
Code selection. Using + + code doesn‘t always select. Without key it’s OK, but slow and annoying. Especially when selecting @Formulas: editor displays “@” as not selected, but if you do the action (copy or cut) you realize that it was selected. So when looking at highlighted code you can not understand which fragment is really selected.
Field colors. You set them – it‘s OK. But somehow and don‘t even know when, the color turns back to black. Maybe after reopening or cursor passing (but not always).
Code compilation. Why there is a need to compile code when passing to another function (i.e. Library left side pane)? You just start typing the code, want to check on the other function on same library, and compiler says „Stop“, you can‘t exit current function – it‘s buggy. The same is when I want to close the library and press - compiler starts compiling it and only after finishing asks if I want to save. Believe me, when there are huge classes from several layers, browsing on them when designer starts compiling all the code, is really inefficient.
Debugger. Why current LotusScript line has to be the last on debug window? If you scroll, the next step over places it on the bottom anyway. You can not see next lines.
Undo. That function would be really funny if it wasn‘t part of your job. That’s not R6 problem it was in R5 also. Interesting, is it so difficult to have an accurate undo function at least for last change? If you delete one word – it‘s OK, If you delete one line – undo will also repair that. But if you only move the cursor or typed something … bye bye your code. The deleted code fragment will be placed in the place where you least expected that. All code is ruined, the only way is to close the library and reopen it having last successful save. For example, I can always rely on MS Word undo – I know it will restore my previous version of document. Maybe that eats a bit more system resources, but I couldn‘t say Notes eats less.
Hide-when formulas. Noticed that on tables. If you change/add hide-when formulas in different cells (especially if you do lots of changes). Save and realize no effect. Then check the formulas – it‘s ok. Close the form, reopen it, and realize that all your changes became only memories.
Change loss. Noticed that sometimes design element doesn‘t save when you edit, press and on save dialog. When reopen, you get an old version of code.
That‘s some of what I could remember right now. Some of these things makes nervous, some makes even angry when you lose your work. If other forum participants would approve and/or update similar behavior of Domino Designer R6, maybe we could draw attention of Lotus Template Development to get these things fixed or at least commented?
For God‘s sake … Notes is what we (most I guess) do for a living…
Yes, you’ve hit upon a number of issues with the Notes client / Domino designer client. Normally I’d say file a bug report for them, but it’s probably worth discussing some of this with other forum members before doing so. Also, the Designer team have been really forthcoming and helpful in this forum, which I for one appreciate. So… ;o)
Agreed. I’ve noticed that modifier keys don’t always “take” in Notes. For example, using ALT to access menus etc. – sometimes I need to try a few times. Weird.
With field colours, my experience is that fields coloured red (usually do this for hidden fields) “lose” the red colour if I go on to edit one of them – if that field is a shared field. It loses its font size setting too.
Code compilation. Heh. We’ve asked for this before: it would be great to be able to save Lotusscript without having to compile it. However, this is a big behavioural change for LS in Designer, so some kind of “screaming-from-the-rooftops-this-is-uncompiled-code” flag would be required in the UI.
Debugger. Not sure what you mean here, sorry. My experience with the debugger is pretty good. The only similar thing I’ve seen is that you can’t always set a breakpoint on code that has been split over more than one line using the “_” character.
Undo. Yes, the undo buffer is inconsistently applied in Notes, and when it does work, has a very short memory, It’s almost non-existent in Designer. We could use more functionality here, definitely.
Hide-when formulas. I haven’t experienced this. The placement and “recall” of hide-whens is far better in ND6.x than it ever was in R5.x (thank goodness).
Design element change “loss”: I haven’t experienced this either I’m afraid. Any design elements in particular?
I assume that Laimonas is talking about that fun you have when the design element note in memory and the one on disk seem to lose their connection; so that when you save your form or view or whatever, it tells you that the note was updated, but it actually wasn’t. After restarting the client, you get an old version of your design note, since it wasn’t updated when you thought.
To be honest, though, I can’t remember that I’ve seen this happen in R6. It sure used to happen a lot in R5, though.
Yes, I noticed that Lotus Designers do participate in this forum, so I hope this (and other) thread will get to the right “recipient”
I don’t mean saving without compilation - that’s not so necessary. I mean: you open the library, just read it, and when closing - it compiles. Designer could ask first if I want to save and only then compile. The problem is that “it thinks” that I changed the code even if I didn’t (scroll down sometimes is enough to mess it’s mind).
Explaining the debugger problem: when “step overing” through lines, the current (next to be executed) line is on the bottom of the screen. If you scroll down to see 2,3 or more steps (lines) after that, next “Step over” again scrolls up. Debugger shouldn’t handle window scroller. That “feature” is new with R6.
Design element change loss. I experencied that with LS libraries.
I’ve experienced the design-element-change loss too many times for it to be funny any more. I now have learned to save and exit in small increments and go back to check if the changes are there.
In my opinion, the N/D Designer client is deficient in both quality and usability.
For example, I wish I could permanently park that #@*&! properties dialog box. No matter where I put it, it’s in the way. And, no matter how many times I close it, it opens when I don’t want it.
As has been shown in this discussion thread, there are too many UI bugs in the designer.
Say what you want about Microsoft, but their IDE for VisualBasic is far easier to use and is rock-solid.
