Forum

Could you also use the override feature as a stop-gap until the library author makes the change?

I have a Belkin SOHO switch and the only issue with Windows 10 is when it reboots and that system is not presently connected to the monitor, it uses default positions (there is no way for it to know, in advance, what resolution I might select in the future). It never moves windows around once

For the Right-Click behavior, you can use Shift+[Right-Click] to have the P&D or Contextual menu ... according to your preferences. So if you choose to use P&D for default action on Right-Click, use Shift+RightClick to get the menu. Then from the menu, you can change the default behavior as well.

<12860_1590835562_5ED2396A_12860_63_1_415479f4-929c-480e-bac4-f297df9c2928@googl groups.com>: > I just rediscovered a routine EV_SCREEN.monitor_area_from_window (a_window: > EV_WINDOW): EV_RECTANGLE which my code was already calling. Doesn't work > however. Investigating... As a small

<26863_1590785543_5ED17607_26863_22_1_1590785542.709125960@f720.i.mail.ru>: > I’m not an expert in Vision library, but given that it’s unclear what > "current screen" means for a window that can be shown at two or more physical > monitors at the same time, would the following work? I don't

I tend to use either - drop the class i want to edit into the editor - ctrl+t for new tab opening and then the above or write the class name into the class input_box - or F6 to go into the class name input_box and then set the class I want to edit Workarounds to your base

Not sure it answers the question, but does ctl+t do? create a new tab... as far as I understand either you get a right click on all interface (all panes) either you got click and drop (which comes with right click) On Wednesday, June 3, 2020 at 7:13:34 PM UTC-4, howard.thomson wrote: > > Hi, >

Jocelyn and Alexander, Thanks, I had removed the files from the project and it compiled. I was hoping to get insight into how to add the feature which you provided in the link. Again thanks. jjj > >

Hi, Does anyone know of a class, or classes, that adapt EiffelVision's text entry field class EV_TEXT_ENTRY for formatted entry ? Such as dates, currency, telephone numbers, credit/debit card numbers ... Howard

Many thx for the very clear explanation On Wednesday, June 3, 2020 at 5:00:23 AM UTC-4, Alexander Kogtenkov wrote: > > It’s OK to access databases, files, sockets, etc. using different SCOOP > processors. But the handles obtained should not be shared. The handles > usually come as opaque

As far as I understand, the classes are 10-years old. Since then Eiffel got iteration forms of loops, and a possibility to iterate over almost all containers. So, possible solutions include: 1. (The best one.) Contact the author of the library and ask to update the code so that it compiles

Hi, You can check https://github.com/jocelyn-contrib/eiffel_gmp/tree/2020-06 I've just updated the code for the upcoming EiffelStudio release. However it may not compile with 19.05 due to the new Unicode aliases (thanks to new multiple alias support). For the new_cursor, you can check https://g

It’s OK to access databases, files, sockets, etc. using different SCOOP processors. But the handles obtained should not be shared. The handles usually come as opaque POINTERs. So, if you clone a FILE object, and read-write-close from different processors, it most likely will be corrupted. If for

Just switched to Eiffel 19.05 on Mac. Program that compile in 18.05 no longer compiles. Using Eiffel_GMP library, not get "Class has deferred feature(s)..." MPZ_RANDOM, MPQ_RANDOM, and MPF_RANDOM have deferred feature `new_cursor' from class ITERABLE. 1) Why am I getting the error now? (I

Many thx, if I understood correctly, correct me if I'm wrong, the strategy you advise is to have one database connection, do the retrieves from there with only one instance (non separate) and then dealing with objects in memory with separate objects if I want. In other words Avoid SCOOP for

You should be very careful with external connections: SCOOP does not automatically protect against double-release of external resources by objects that were obtained by cloning them. So, it’s OK to clone and serialize user objects. But I’d rather avoid doing it with objects used to access

Serialization is rather a heavy-weight solution. I’d stick to creation procedures that accept a separate argument. For more complex cases (including the one used in the initial question), serialization can also be avoided by using a visitor pattern. Alexander Kogtenkov Gachoud Philippe

You can find some simple examples at https://www.eiffel.org/doc/solutions/Persistence%2C_storage%2C_and_retrieval#With_the_SED_persistence_format They use a file, but it should be possible to do everything in memory as soon as functionality of IO_MEDIUM is implemented with some other storage

As a third solution for other cases, would you recommend the make_from_separate feature in all classes when they are not deferred, and serialize when they are, or would you recommend serialization for all? many thx On Tuesday, June 2, 2020 at 3:53:57 AM UTC-4, Alexander Kogtenkov wrote: > > I

Hi Alexander, many thx for your answer, the option 1 would for me simply report the problem for me which is in many of my cases having a parallel part (separate) and a synchronized part (non separate). The problems for me don't occur so much in creating a new separate but on returning into a

I can see two possibilities. Which one is suitable (if any) depends on the application. 1. Change the type of attribute `mother` to be separate. Then every object of type CAT can be separate, but all they share the same `mother` object. This would require additional synchronization when

I'm on a way of trying to get a separate DB_CONNECTION with ODBC. And its really difficult for me to realize that base_selection has to have some make_from_separate methods, as much as the cursor to access the data, as much as base_update, none of these classes seem to be prepared for SCOOP or

Hello everybody, still scooping I'm struggling with following problem, hope its self explanatory otherwise I explain it above: deferred class FEMALE end - - class FEMALE class CAT feature {NONE} -- Initialize make_from_separate (other: separate like Current) do

This new release of Gobo Eiffel should work fine with EiffelStudio 19.05 and 19.12. Please see the release notes here: https://github.com/gobo-eiffel/gobo/blob/master/History.md You can download the Gobo package from SourceForge: https://sourceforge.net/projects/gobo-eiffel/files/gobo

I just rediscovered a routine EV_SCREEN.monitor_area_from_window (a_window: EV_WINDOW): EV_RECTANGLE which my code was already calling. Doesn't work however. Investigating... On Friday, 29 May 2020 21:52:25 UTC+1, Alexander Kogtenkov wrote: > > I’m not an expert in Vision library, but given that